703_sec2 copy - SOFTWARE DESIGN: SECTION 2 - Process Models...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
703/sec2/tsem 12/27/09 1 SOFTWARE DESIGN: SECTION 2 - Process Models Tom Maibaum CAS Room 159 ITB ext 26627 tom@maibaum.org
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ASE/sec2/tsem 12/27/09 2 SECTION 2: Introduction In any engineering domain, the following questions must be answered in the process of constructing artifacts: What is the problem to be solved? What are the characteristics of the entity to be used to solve the problem? How will the entity and the solution be realised? How will the entity be constructed ? What approach will be used to uncover errors ? How will the entity be supported in the long term, when servicing, training, correction, adaptation and enhancement are required?
Background image of page 2
ASE/sec2/tsem 12/27/09 3 Section 2: Introduction What is SE? What is SW? The answers to these questions help us to characterise SE and the nature of the methods and tools which are appropriate to its practice. Traditionally, engineering consists of 3 activities related to the construction of artifacts which fulFl a required need: design manufacture use Of these, only the 1st and 3rd play an important role for SW.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ASE/sec2/tsem 12/27/09 4 Section 2: Introduction SW is a logical rather than a physical system element. Hence: the major up front activity related to SW is design SW does not wear out most SW is custom built , rather than being assembled from existing components A particular difFculty for SW construction is that we do not have a clear understanding yet of the SW production process .
Background image of page 4
ASE/sec2/tsem 12/27/09 5 Section 2: Introduction SE work can be categorised into 3 phases, independently of the application/problem: defnition phase : focuses on the what ; development phase : focuses on the how ; maintenance phase : focuses on change that is associated with error correction, adaptation due to evolving environment, changing customer requirements. Four types of change are encountered during maintenance: corrective maintenance adaptive maintenance perFective maintenance preventive maintenance/soFtware reengineering
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ASE/sec2/tsem 12/27/09 6 Section 2: Introduction A number of umbrella activities complement these phases: software project tracking and control formal technical reviews software quality assurance software conFguration management document preparation and production reusability management measurement risk management
Background image of page 6
ASE/sec2/tsem 12/27/09 7 Section 2: The SW Process We assume that the process of planning, developing and maintaining SW is seen in the context of a well deFned engineering process . All projects (at least within a single organisation) should have a
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 23

703_sec2 copy - SOFTWARE DESIGN: SECTION 2 - Process Models...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online