Post-Delivery Phase

Your client's sign-off on the Web site project initiates the final stage of the Web site development process, the Post-Delivery phase. The goal of this phase is to maintain and update the site. Activities in this phase are often performed by your client's organization; however, there may be an arrangement for the development team (or another outsourcing provider) to maintain the site.

As with any Web design team, WebTeam's work does not end in Post-Delivery, even though the client has signed off on the project. Maintenance agreements are common between the client and design team; and if the client wants to upgrade, there is a good chance that they will turn to the team that built the original site; and the development cycle reverts to phase 1. Click the WebTeam group to find the objectives, deliverables, and activities assigned for the Post-Delivery phase.

1. 1st phase tab = Discovery ,
2. 2nd phase tab = Definition
3. 3rd phase tab =Design ,
4. 4th phase = Development
5. 5th phase tab = Delivery , and
6. 6th phase tab, Post-Delivery.

OBJECTIVES	DELIVERABLES	Activities
Obtain client sign-off Develop new business opportunities	Formal sign-off New statements of need	Perform gap analysis by comparing the product to client's business requirements Analyze Web metrics (evidence of success)

ROLE	OBJECTIVES	DELIVERABLES	Activities
Creative	Ensure that multimedia and graphic components remain current and functional	Updated components as required	Update multimedia components as necessary Update graphics as necessary Ensure that branding stays intact

If your project uses Rational ClearCase MultiSite to share source data with developers in other geographical locations, and if the project streams are mastered at a different site, you are notified that the development stream has been assigned the posted status. Notify the project integrator at the site that masters the integration stream replica. The project integrator can then continue the operation or cancel it to return the development stream to its previous state. If you post your work, only someone at the master site can cancel or complete the operation. If your project uses Rational ClearCase MultiSite and the UCM integration with Rational ClearQuest, your project manager can set the Do ClearQuest Action After Delivery policy. All activities being delivered must be mastered by the same PVOB replica that masters the target stream. If the project manager sets the Check Mastership "Before Delivery policy" and if the deliver operation is local and all activities being delivered are not mastered locally, the deliver operation fails. If the deliver operation is remote, the Check Mastership Before Delivery policy causes the following behavior:

Internet project managers oversee the development of websites, online databases, intranets, and other networking solutions. They are expected to earn at least a bachelor's degree in computer science or a related field before beginning their careers, though earning a Master of Business Administration (MBA) can enhance opportunities to advance into management. Salaries in this field vary greatly, depending on the job and the certifications held. Job opportunities are expected to increase through 2022, according to the U.S. Bureau of Labor Statistics (BLS), especially in hospitals.

• The importance of Project Stakeholder Management
  Stakeholders are an important part of the project management framework. Stakeholders request projects, approve them, reject them, support them, and oppose them. Because stakeholder management is so important to project success, the Project Management Institute decided to create an entire knowledge area devoted to it. Many of the concepts related to communications and human resource management also apply to stakeholder management, but unique activities are required to perform good stakeholder management. The purpose of project stakeholder management is to identify all people or organizations affected by a project, to analyze stakeholder expectations, and to effectively engage stakeholders in project decisions throughout the life of a project. Project managers and their teams must have a good dialogue with stakeholders and address issues as they occur to ensure stakeholder satisfaction.
• Projects Change: Projects often cause changes in organizations, and some people may lose their jobs when a project is completed. For example, a project might create a new system that makes some jobs obsolete, or a project might result in outsourcing work to an external group to make the organization more efficient. The project managers might be viewed as enemies by these stakeholders and other negatively affected stakeholders. By contrast, some people may view project managers as allies if they lead a project that helps increase profits, produce new jobs, or increase pay for certain stakeholders. In any case, project managers must learn to identify, understand, and work with a variety of stakeholders.

The post delivery phase from a database administrators point of view involves the following points. Each of the four elements below must be considered after the initial implementation of the data model.

1. Have the business rules changed and does the corresponding data model need to be changed?
2. If the data model has changed, which tables in the data model will be affected?
3. Do any depencies in the existing tables need to be altered?
4. Do the tables have to be normalized?

• How do business rules affect the tables of a data model Business rules can affect the tables of a data model by determining the relationships between the tables, the types of data that can be stored in each table, and the constraints that must be enforced on the data. For example, a business rule may dictate that a customer can only have one active account, which would translate to a one-to-one relationship between the customer table and the account table in the data model. Additionally, business rules can also dictate specific data validation and integrity constraints, such as ensuring that a credit card number is in the correct format or that a date of birth is in the past. These constraints would need to be implemented in the database schema to enforce the business rules.

In a traditional relational database, the user begins by specifying a series of column types and names for a table. Information is then added as rows of values, with each of those named columns as a cell of each row. You cannot have additional values that were not specified when you created the table, and every value must be present, even if it is as a NULL value.
Document stores instead let you enter each record as a series of names with associated values, which you can picture being like a JavaScript object, a Python dictionary, or a Ruby hash. You do not specify ahead of time what names will be in each table using a schema. In theory, each record could contain a completely different set of named values, though in practice, the application layer often relies on an informal schema, with the client code expecting certain named values to be present.
The key advantage of this document-oriented approach is its flexibility. You can add or remove the equivalent of columns with no penalty, as long as the application layer does not rely on the values that were removed. A good analogy is the difference between languages where you declare the types of variables ahead of time, and those where the type is inferred by the compiler or interpreter. You lose information that can be used to automatically check correctness and optimize for performance, but it becomes a lot easier to prototype and experiment.

• Case Study: The Web Site Development Process in Action
  1. Look at a commercial web site (macys.com, www.sears.com, ual.com).
  2. What do you think are the business requirement of the site?
  3. How well has ea ch role (biz, create, tech) met those requirements?
  4. Which features of the interface might creative have designed? Technical?
  5. List 2 e-commerce features of the site.
  6. For each of the 6 phases, list an activity that one of the Roles (biz, create, tech) might have performed during that phase as one or both of the e-commerce features you found were developed.

The next lesson is the module conclusion.