Software Engineering Process
Definitions and context
Software Engineering Process
| Software engineering process concepts | Process infrastructure | Process measurement |
|
|
|
| Process definition | Qualitative process analysis | Process implementation and change |
|
|
|
IEEE Life Cycle Processes
| IEEE Std. 12207.0-1996 | Software Life Cycle Processes |
| IEEE Std. 12207.1-1997 | Software Life Cycle - Life Cycle Dates |
| IEEE Std. 12207.2-1997 | Software Life Cycle Processes - Implementation considerations |
| IEEE Std. 1074 | IEEE Standard for Developing Life Cycle Processes |
IEEE 1074: Standard for Developing Life Cycle Processes
| Process group | Processes | Clause | Activities |
| Life Cycle Modeling | Selection of a Life Cycle Model | ||
| Project Management | Project Initiation | 3.1.3 3.1.4 3.1.5 3.1.6 |
3 Map Activities to Software Life Cycle Model
4 Allocate Project Resources 5 Establish Project Environment 6 Plan Project Management |
| Project Monitoring and Control | 3.2.3
3.2.4 3.2.5 3.2.6 3.2.7 |
Analyze Risks Perform Contingency Planning
Manage the Project Retain Records Implement Problem Reporting Model |
|
| Software Quality Management | 3.3.3
3.3.4 3.3.5 3.3.6 |
Plan Software Quality Management
Define Metrics Manage Software Quality Identify Quality Improvement Needs |
|
| Pre-development | Concept Exploration | 4.1.3
4.1.4 4.1.5 4.1.6 4.1.7 |
Identify Ideas or Needs
Formulate Potential Approaches Conduct Feasibility Studies Plan System Transition (If Applicable) Refine and Finalize the Idea or Need |
| System Allocation | 4.2.3
4.2.4 4.2.5 |
Analyze Functions
Develop System Architecture Decompose System Requirements |
|
| Development | Requirements | 5.1.3
5.1.4 5.1.5 |
Define and Develop Software Requirements
Define Interface Requirements Prioritize and Integrate Software Requirements |
| Design | 5.2.3
5.2.4 5.2.5 5.2.6 5.2.7 |
Perform Architectural Design
Design Data Base (If Applicable) Design Interfaces Select or Develop Algorithms (If Applicable) Perform Detailed Design |
|
| Implementation | 5.3.3
5.3.4 5.3.5 5.3.6 5.3.7 5.3.8 |
Create Test Data
Create Source Generate Object Code Create Operating Documentation Plan Integration Perform Integration |
|
| Post-development | Installation | 6.1.3
6.1.4 6.1.5 6.1.7 |
Plan Installation
Distribution of Software Installation of Software Accept Software in Operational Environment |
| Operation and Support | 6.2.3
6.2.4 6.2.5 |
Operate the System
Provide Technical Assistance and Consulting Maintain Support Request Log |
|
| Maintenance | 6.3.3 | Reapply Software Life Cycle | |
| Retirement | 6.4.3
6.4.4 6.4.5 |
Notify Users
Conduct Parallel Operations (If Applicable) Retire System |
|
| Integral Processes | Verification and Validation | 7.1.3
7.1.4 7.1.5 7.1.6 7.1.7 7.1.8 |
Plan Verification and Validation
Execute Verification and validation Tasks Collect and Analyze Metric Data Plan Testing Develop Test Requirements Execute Tests |
| Software Configuration
Management |
7.2.3
7.2.4 7.2.5 7.2.6 |
Plan Configuration Management
Develop Configuration Identification Perform Configuration Control Perform Status Accounting |
|
| Document Development | 7.3.3
7.3.4 7.3.5 |
Plan Documentation
Implement Documentation Produce and Distribute Documentation |
|
| Training | 7.4.3
7.4.4 7.4.5 7.4.6 |
Plan the Training Program
Develop Training Materials Validate the Training Programs Implement the Training Program |
Software Development Life Cycle (SDLC)
Like any other engineering products, software products are oriented towards customers. It is either market driven or it drives the market. Customer Satisfaction was the buzzword of the 80's. Customer Delight is today's buzzword and Customer Ecstasy is the buzzword of the new millennium. Products that are not customer (user) friendly have no place in the market although they are engineered using the best technology. The interface of the product is as crucial as the internal technology of the product.
Market Research
A market study is made to identify a potential customer's need. This process is also known as market research. Here, the already existing need and the possible/potential needs that are available in a segment of the society are studied carefully. The market study is done based on a lot of assumptions. Assumptions are the crucial factors in the development or inception of a product's development. Unrealistic assumptions can cause a nosedive in the entire venture. Though assumptions are abstract, there should be a move to develop tangible assumptions to come up with a successful product.
Research and Development
Once the Market study is made, the customer's need is given to the Research and Development (R&D) Department to conceptualize a cost-effective system that could potentially solve customer's needs better than the competitors. Once the conceptual system is developed and tested in a hypothetical environment, the development team takes control of it. The development team adopts one of the software development methodologies that is given below, develops the proposed system, and gives it to the customers.
The Marketing group starts selling the software to the available customers and simultaneously works in developing a niche segment that could potentially buy the software. In addition, the marketing group passes the feedback from the customers to the developers and the R&D group to make possible value additions in the product.
While developing a software, the company outsources the non-core activities to the other companies who specialize in those activities. This accelerates the software development process largely. Some companies work on tie-ups to bring out a highly matured product in a short period.
Following are the basic popular models used by many software development firms.
- System Development Life Cycle (SDLC) Model
- Prototyping Model
- Rapid Application Development Model
- Component Assembly Model
System Development Life Cycle Model (SDLC Model)
This is also known as Classic Life Cycle Model (or) Linear Sequential Model (or) Waterfall Method. This has the following activities.
- System/Information Engineering and Modeling
- Software Requirements Analysis
- Systems Analysis and Design
- Code Generation
- Testing
- Maintenance
System/Information Engineering and Modeling
As software is always of a large system (or business), work begins by establishing requirements for all system elements and then allocating some subset of these requirements to software. This system view is essential when software must interface with other elements such as hardware, people and other resources. System is the basic and very critical requirement for the existence of software in any entity. So if the system is not in place, the system should be engineered and put in place. In some cases, to extract the maximum output, the system should be re-engineered and spruced up. Once the ideal system is engineered or tuned, the development team studies the software requirement for the system. Software Requirement Analysis
This is also known as feasibility study. In this phase, the development team visits the customer and studies their system. They investigate the need for possible software automation in the given system. By the end of the feasibility study, the team furnishes a document that holds the different specific recommendations for the candidate system. It also includes the personnel assignments, costs, project schedule, and target dates. The requirements gathering process is intensified and focussed specially on software. To understand the nature of the program(s) to be built, the system engineer ("analyst") must understand the information domain for the software, as well as required function, behavior, performance and interfacing. The essential purpose of this phase is to find the need and to define the problem that needs to be solved.
System Analysis and Design
In this phase, the software development process, the software's overall structure and its nuances are defined. In terms of the client/server technology, the number of tiers needed for the package architecture, the database design, the data structure design etc are all defined in this phase. A software development model is created. Analysis and Design are very crucial in the whole development cycle. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase. The logical system of the product is developed in this phase.
Code Generation
The design must be translated into a machine-readable form. The code generation step performs this task. If the design is performed in a detailed manner, code generation can be accomplished without much complication. Programming tools like Compilers, Interpreters, Debuggers are used to generate the code. Different high level programming languages like C, C++, Pascal, Java are used for coding. With respect to the type of application, the right programming language is chosen.
Testing
Once the code is generated, the software program testing begins. Different testing methodologies are available to unravel the bugs that were committed during the previous phases. Different testing tools and methodologies are already available. Some companies build their own testing tools that are tailor made for their own development operations.
Maintenance
Software will definitely undergo change once it is delivered to the customer. There are many reasons for the change. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period.
Prototyping Model
This is a cyclic version of the linear model. In this model, once the requirement analysis is done and the design for a prototype is made, the development process gets started. Once the prototype is created, it is given to the customer for evaluation. The customer tests the package and gives his/her feed back to the developer who refines the product according to the customer's exact expectation. After a finite number of iterations, the final software package is given to the customer. In this methodology, the software is evolved as a result of periodic shuttling of information between the customer and developer. This is the most popular development model in the contemporary IT industry. Most of the successful software products have been developed using this model - as it is very difficult (even for a whiz kid!) to comprehend all the requirements of a customer in one shot. There are many variations of this model skewed with respect to the project management styles of the companies. New versions of a software product evolve as a result of prototyping.
Rapid Application Development (RAD) Model
The RAD is a linear sequential software development process that emphasizes an extremely short development cycle. The RAD software model is a "high speed" adaptation of the linear sequential model in which rapid development is achieved by using a component-based construction approach. Used primarily for information systems applications, the RAD approach encompasses the following phases:
Business modeling
The information flow among business functions is modeled in a way that answers the following questions:
- What information drives the business process?
- What information is generated?
- Who generates it?
- Where does the information go?
- Who processes it?
Data modeling
The information flow defined as part of the business modeling phase is refined into a set of data objects that are needed to support the business. The characteristic (called attributes) of each object is identified and the relationships between these objects are defined.
Process modeling
The data objects defined in the data-modeling phase are transformed to achieve the information flow necessary to implement a business function. Processing the descriptions are created for adding, modifying, deleting, or retrieving a data object.
Application generation
RAD assumes the use of the RAD tools like VB, VC++, Delphi etc rather than creating software using conventional third generation programming languages. The RAD works to reuse existing program components (when possible) or create reusable components (when necessary). In all cases, automated tools are used to facilitate construction of the software.
Testing and turnover
Since the RAD process emphasizes reuse, many of the program components have already been tested. This minimizes the testing and development time.
Component Assembly Model
Object technologies provide the technical framework for a component-based process model for software engineering. The object oriented paradigm emphasizes the creation of classes that encapsulate both data and the algorithm that are used to manipulate the data. If properly designed and implemented, object oriented classes are reusable across different applicationsand computer based system architectures. Component Assembly Model leads to software reusability. The integration/assembly of the already existing software components accelerate the development process. Nowadays many component libraries are available on the Internet. If the right components are chosen, the integration aspect is made much simpler.
Conclusion
All these different software development models have their own advantages and disadvantages. Nevertheless, in the contemporary commercial software evelopment world, the fusion of all these methodologies is incorporated. Timing is very crucial in software development. If a delay happens in the development phase, the market could be taken over by the competitor. Also if a 'bug' filled product is launched in a short period of time (quicker than the competitors), it may affect the reputation of the company. So, there should be a tradeoff between the development time and the quality of the product. Customers don't expect a bug free product but they expect a user-friendly product. That results in Customer Ecstasy!
