a) The PMP b) The reliability program plan c) The integrated logistic support plan The purpose of the Software Engineering Management Plan is to develop the policies, procedures and structure in order to foster the support activities and engineering activities required for design and development process of the system. Systems Engineering Management Plan is developed in the conceptual design phase of the life cycle process when the need for the management related requirement arises. SEMP relationship with each of the following: a) The PMP: PMP document will explain about the deliverables, overall tasks with its inputs, approach for performing tasks and its output and schedule required to complete project. The program management plan will serve as the input to SEMP. Based on the information available in PMP, SEMP will be able to prepare a top level plan required for managing systems engineering effort.
Unified Software Development Model: Unified software development model is modified for the specific software product to be developed i.e. it is an adaptable methodology. Unified software development model consist four phases and five core workflows. The phases are inception phase, elaboration phase, construction phase and transition phase and workflows are requirement, analysis, design, implementation and test workflow. These phases and workflows correspond to increments of project as it develops.
Meetings with managers, stake holders and users are held in order to determine the requirements. Who is going to use the system? How will they use the system? What data should be input into the system? What data should be output by the system?
What do we want to accomplish? If a project is called for, the project definition stage identifies general objectives, specifies the scope of the project and develops a project plan that can be shown to management. Stage 2 - Systems Study This stage analyzes the problems of the existing system (manual or automated) in detail, identifies objectives to be attained by a solution to these problems, and describes alternative solutions. The systems study phase examines the feasibility of each solution alternative for review by management. The following questions are answered: What do the existing systems do?
These diagrams are used to show how data flows through the organization. This acquired information can be used to achieve business process reengineering as well as a road map for the programming team. Once the development team knows what the new system requires to solve the problem the systems design stage can begin. • Systems design: The goal of this phase is to describe desired features and operations in detail including what specific functions it should have and what parts it should contain. There are two main areas of system design.
What data should be output by the system? These are general questions that get answered during a requirements gathering phase. After requirement gathering these requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be development is also studied. Finally, a Requirement Specification document is created which serves the purpose of guideline for the next phase of the model. REQUIREMENTS GATHERING AND ANALYSIS REQUIREMENT GATHERING AND ANALYSIS Business requirements are gathered in this stage.
The functional model represents the methods of the system from the perspective of data flow.” After the analysis phase the system design phase takes place. Here the system is sub-categorized and appointed tasks and persistent data storage is established, also within this phase the architecture is formed. Lastly the object design phase starts and is where the implementation plan is established and algorithms and object classes are also
Three aspects we will discuss for software quality which are functional quality, structural quality and process quality. Figure 6. Software quality A. Functional quality Software functional quality is based on functional requirements or specification. This phase is meeting with specific requirements to achieve the goal in development process.  B.
One aspect of analysis is defining the boundaries of the system and determining whether or not a candidate system should consider other related systems. During analysis, data are collected on the available files, decision points, and transactions handled by the present system. Logical system models and tools that are used in analysis are Training, experience, and common sense are required for collection of the information needed to do the analysis. 2.2 SOFTWARE REQUIREMENT SPECIFICATION: 2.2.1 USER REQUIREMENT: User satisfaction is most important in the development of product. User