Scribd
Upload
36 views5 pages

CH 2

Uploaded by

Omar Al abbasy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
36 views5 pages

CH 2

Uploaded by

Omar Al abbasy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 5
CS 410/510 - Software Engineering Software Processes Reference: Sommerville, Software Engineering, 10 ed., Chapter 2 The big picture ‘A software process is a structured set of activities required to develop a software system. Note that we are talking about a "software process" -- not a "software development process." ‘There are many different kinds of software processes, but each and every one of them involve these four types of fundamental activities: + Software specification - defining what the system should do; + Software design and implementation - defining the organization of the system and implementing the system; + Software validation - checking that it does what the customer wants; + Software evolution - changing the system in response to changing customer needs, A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective. When we describe and discuss software processes, we usually talk about the activities in these processes such as specifying a data model, designing a user interface, etc, and the ‘ordering of these activities. Process descriptions may also include + Products (what), which are the outcomes of a process activity; + Roles (who), which reflect the responsibilities of the people involved in the process; ‘+ Pre- and post-conditions (how), which are statements that are true before and after a process activity has been enacted or a product produced. Plan-driven processes are processes where all of the process activities are planned in advance and progress is measured against this plan. In agile processes, planning is incremental and it is easier to change the process to reflect changing customer requirements. In practice, most practical processes include elements of both plan-driven and agile approaches, Software process models ‘The waterfall model Plan-driven model. Separate and distinct phases of specification, software design, implementation, testing, and maintenance. Incremental development Specification, development and validation are interleaved. The system is developed as a series of, versions (increments), with each version adding functionality to the previous version. May be plan- driven or agile. Integration and configuration Based on the existence of a significant number of reusable components/systems. The system development process focuses on integrating these components into a system rather than developing them from scratch. May be plan-driven or agile. In practice, most large systems are developed using a process that incorporates elements from all of these models The waterfall model ‘System and software design ‘implementation and unit testing ‘integration and system testing ‘Operation and maintenance There are separate identified phases in the waterfall model: Requirements analysis and definition The system's services, constraints, and goals are established by consultation with system users. They are then defined in detail and serve as a system specification. System and software design The systems design process allocates the requirements to either hardware or software systems by establishing an overall system architecture, Software design involves identifying and describing the fundamental software system abstractions and thei relationships. Implementation and unit testing During this stage, the software design is realized as a set of programs or program units. Unit testing involves verifying that each unit meets its specification, Integration and system testing ‘The individual program units or programs are integrated and tested as a complete system to ensure that the software requirements have been met. After testing, the software system is delivered to the customer. Operation and maintenance Normally (although not necessarily), ths isthe longest life cycle phase. The system is installed and put into practical use. Maintenance involves correcting errors which were not discovered in earlier stages ofthe life cycle, improving the implementation of system units and enhancing the system's services as new requirements are discovered. ‘The main drawback of the waterfall model is the difficulty of accommodating change after the process is, underway. In principle, a phase has to be complete before moving onto the next phase. Waterfall model problems inciude: Difficult to address change Inflexible partitioning of the project into distinct stages makes it difficult to respond to changing customer requirements. Therefore, this model is only appropriate when the requirements are well understood and changes will be fairly imited during the design process. Few business systems have stable requirements, Very few real-world applications ‘The waterfall model is mostly used for large systems engineering projects where a system is developed at several sites, In those circumstances, the plan-driven nature of the waterfall model helps coordinate the work. Incremental development model Concurrent activities Specification > | intermediate Benefits of incremental development: Lower cost of changes ‘The cost of accommodating changing customer requirements is reduced. The amount of analysis and documentation that has to be redone is much less than is required with the waterfall model Frequent feedback Its easier to get customer feedback on the development work that has been done. Customers can ‘comment on demonstrations of the software and see how much has been implemented. Faster delivery More rapid delivery and deployment of useful software to the customer is possible. Customers are able to use and gain value from the software earlier than is possible with a waterfall process. Problems with incremental development (from the management perspective): The process is not visible Managers need regular deliverables to measure progress. If systems are developed quickly, itis not cost-effective to produce documents that reflect every version of the system. ‘System structure tends to degrade as new increments are added Unless time and money is spent on refactoring to improve the software, regular change tends to corrupt its structure, Incorporating further software changes becomes increasingly dificult and costly. Integration and configuration Aopliaton syste = ‘salable ascorey Regulemens ‘specietion Components ‘malate negate ‘stem Devwpnew >) | components ‘This approach is based on systematic reuse where systems are integrated from existing components or COTS (Commercial-off-the-shelf) systems. Process stages include: Component analysis; Requirements modification; System design with reuse; Development and integration. Reuse is now the standard approach for building many types of business system. ‘Types of software components: + Web services that are developed according to service standards and which are available for remote Invocation. + Collections of objects that are developed as a package to be integrated with a component framework such as .NET or J2EE. + Stand-alone commerci environment. I-off-the-shelf systems (COTS) that are configured for use in a particular Software process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities with the overall goal of specifying, designing, implementing and testing a software system, ‘The four basic process activities of specification, development, validation and evolution are organized

You might also like