Prepare For System Initiation

Purpose
The purpose of Prepare for System initiation is to ensure that the Project Team, and the environment in which it will operate, are ready for successful completion of this phase.

Description
In addition to the Project Manager, Business Analyst and Technical Lead roles are required to complete the team for this phase.

“Identification, assignments and orientation of new team members required for this phase is activates in project Initiation in the project management lifecycle.”

“A record of prior efforts to develop a similar system (including current system documentation, if it is a replacement) can also be very helpful, although you should take care not to pro-judge the approach either because of, or in spite of, prior experiences.”

Introduction to System Initiation

Purpose
The purpose of System Initiation is to validate the proposed Solutions developed. In this phase, the broad parameters of the new system are defined, and applicable system development activates is identified.

Once the overall approach has been confirmed , it is necessary to estimate the effort and resource required for the next phase in elemental detail, and to provide high-level estimates for subsequent phase, to the extent necessary to support the project management lifecycle deliverable and activates of project Initiation.

List of processes
This phase consists of the following processes

Prepare for System initiation, where the initial members of the Project Team familiarize themselves with the project’s defining documents and plan the activates for the rest of the phase;

Validate Proposed Solution, where the original System requirements Analysis schedule is developed approach are validated;

Developed System Schedule, where a detailed System Requirements Analysis schedule is developed, and a high-level system developed schedule is produced.

List of Roles
The following roles are involved in carrying out the processes of this phase.
• Project Manager
• Project Sponsor
• Business Analyst
• Technical Lead

SYSTEM INITATION

In this section you will learn:

• Introduction to System Initiation -->http://sdlcandss.blogspot.com/2010/01/introduction-to-system-initiation.html

• Prepare For System Initiation-->http://sdlcandss.blogspot.com/2010/01/prepare-for-system-initiation.html

• Validate Proposed Solutions

• Develop System Schedule

• Measurements of success

INTRO to SDLC

SDLC ~ Software Development Life Cycle

Software Development Life Cycle Overview

All projects should progress through the same six phases :

Phase 1 : System Initiation

The Business case and Proposed Solution developed during project Origination are re-examined to ensure that they are still appropriately defined and address a existing organisation need. This validation effort provides the project team with the basis for a detailed schedule defining the steps needed to obtain a thorough understanding of the business requirement and an initial view of staffing needs.

Phase 2 : System requirements Analysis

The needs of the business are captured in as much detail as possible. The project Manager leads the project team in working with the Customers to define what it is that the new system must do.By obtaining a detailed and comprehensive understanding of the business requirements, the Project Team can develop the Functional Specifications that will drive the system design.

Phase 3: System Design

Which builds upon the work performed during System requirement Analysis, and results in a translational of the functional requirements into a complete technical solutions. This solution dictates the technical architecture, standards, specifications and strategies to be followed throughout the building, testing, and implementation of the system. The completion of the System Design also marks the point in the project at which the project Manager should be able to plan, in detail, all future projects phases.

Phase 4: System Construction

Throughout which the Project Team builds and tests the various modules of the applications, including any utilities that will be needed during System Acceptance and System implementation . As system components are built, they will be tested both individually and in logical related and integrated grouping util such time as a full system test has been performed to validate functionality. Documentation and training materail are also developed during this phase.

Phase 5: System Acceptance

During which the focus of the system validate effort shifts from those team members responsible for the developing the application to those who will ultimately use the system in the execution of their daily responsible. In addition to confirming that the system meets functional expectations, activities are aimed at validating all aspects of conversion and system deployment.

Phase 6: System Implementation

The final phase of the lifecycle, which comprises all activities associated with the deployment of the application. These effort including training, installation of the system in a production settings, and transitions of the application from the project Team to the Performing Organisation.

Lets see all these six stages in detail in the other posts.

Software Quality Assurance

Software quality assurance provides the foundation on which all system development activities should occur so that the highest quality possible will be delivered. According to the IEEE Standards Glossary of Software Engineering Terminology, quality is defined as the degree to which a system, components, or process meets specified requirements and Customer needs and expectations.

Software Quality Standerds

Software Quality Standards define the Programing Standards, and developmenst/testing standards to be followed thorouhght the projects.

Software Quality Assurance process defines practices and produces to be used by the Project Team to meet the quality standards, and to provide management with evidence that these procedures are being followed.

Software Quality Controls

Software Quality Controls comprises a series of reviews and audits evaluate deliverable with respect to defined standards and acceptance criteria.These controls include software testing techniques and peer reviews.

The key to these SQA efforts is that must be performed throughout all phases of the projects. In addition, all SQA efforts should ideally be performed by a third party, Independent from the team members responsible for delivering the system. Availability of the staff and budget are two factors that must be considered in determining the feasibility of applying an independent SQA Analyst or team to the projects.