written 6.8 years ago by | modified 2.8 years ago by |
Subject: Software Engineering
Topic: Introduction to Software Engineering
Difficulty: High
written 6.8 years ago by | modified 2.8 years ago by |
Subject: Software Engineering
Topic: Introduction to Software Engineering
Difficulty: High
written 6.7 years ago by |
A process framework established the foundation for a complete software process by identifying a small number of frame work activities that are applicable to all software projects, regardless of their size or complexity. In addition, the process framework encompasses a set of umbrella activities that are applicable across the entire software process.
The following generic process framework is applicable to the vast majority of software projects:
Communication: This frame work activity involves heavy communication and collaboration with the customer and encompasses requirements gathering and other related activities.
Planning: This activity establishes a plan for software engineering work that follows. It describes the technical tasks to be conducted, the risks that are likely, the resources that will be required, the work products that are to be produced, and a work schedule which is to be followed.
Modeling: The activity encompasses the creation of models that allow the developer and the customer to better understand software requirements and the design that will achieve those requirements.
Construction:This activity combines code generation and the testing that are required to uncover errors in the code.
Development:. The software is delivered to the customer who evaluates the delivered products and provides feedback based on the evaluation.
The framework described in the generic view of software engineering is complimented by a number of umbrella activities. Typical activities in this category include:
Software project tracking and control- allows the software team to access progress against the project plan and take necessary actions to maintain schedule.
Risk management- assesses risk that may affect the outcome of the projects or the quality of the product.
Software quality assurance- defines and conducts the activities required to ensure software quality.
Formal technical review- assesses software engineering work products in an effort to uncover and remove errors before they are propagated to the next actions or activity.
Measurement- defines and collects process, project, and product measures that assist the tam in delivering software that meets customer’s needs: can be used in conjunction with all other framework and umbrella activities.
Software configuration management- manages the effects of change throughout the software process.
Re usability management- defines criteria for work products reuse (including software components) and establishes mechanisms to achieve reusable components.