The document describes the final stages of an installation project. It discusses locking the project record which includes archiving the software items, implementation map, source code, and documentation for future reference. It then discusses the maintenance process, including requirement studies, understanding documentation, training employees on assigned work, and how maintenance has no defined end like an umbrella. Finally, it introduces the system architecture diagram showing a three-tier architecture with presentation, business logic, and data layers to handle requests from users to the database through servers.
The document describes the final stages of an installation project. It discusses locking the project record which includes archiving the software items, implementation map, source code, and documentation for future reference. It then discusses the maintenance process, including requirement studies, understanding documentation, training employees on assigned work, and how maintenance has no defined end like an umbrella. Finally, it introduces the system architecture diagram showing a three-tier architecture with presentation, business logic, and data layers to handle requests from users to the database through servers.
The document describes the final stages of an installation project. It discusses locking the project record which includes archiving the software items, implementation map, source code, and documentation for future reference. It then discusses the maintenance process, including requirement studies, understanding documentation, training employees on assigned work, and how maintenance has no defined end like an umbrella. Finally, it introduces the system architecture diagram showing a three-tier architecture with presentation, business logic, and data layers to handle requests from users to the database through servers.
he primary outputs of the installation and acceptance stage include a
production application, a completed acceptance test suite, and a
memorandum of customer acceptance of the software. Finally, the PDR enters the last of the actual labor data into the project schedule and locks the project as a permanent project record. At this point the PDR "locks" the project by archiing all software items, the implementation map, the source code, and the documentation for future reference. Maintenance: !uter rectangle represents maintenance of a project, "aintenance team will start with re#uirement study, understanding of documentation later employees will be assigned work and they will under go training on that particular assigned category. For this life cycle there is no end, it will be continued so on like an umbrella $no ending point to umbrella sticks%. 2.4 SYSTEM ARCHITECTURE Architecture flow: &elow architecture diagram represents mainly flow of re#uests from users to database through serers. 'n this scenario oerall system is designed in three tires separately using three layers called presentation layer, business logic layer and data link layer. (his project was deeloped using )*tire architecture. SERVER User Dat a Bas e Request Response