QUESTIONS AND
ANSWERS
FOR ASSISTANCE CONTACT
EMAIL:gabrielmusyoka940@gmail.com
, lOMoARcPSD|31863004
Learning Unit 1: Chapter 2 & 3
Objectives:
1. Explain the fundamental concepts of software processes
Software is a product designed and built by software engineers.
A set of related activities that leads to production of a software product
Multiple processes, but four activities that’re fundamental to Software engineering:
i. Specification: Defining what the system should do
ii. Design and implementation: Defining the organisation of the system and implementing the
system.
iii. Validation: Checking the system performs in accordance with customer needs
iv. Evolution: Changing the system in response to changing customer needs
Process model: Abstract representations of a process, essentially the activities that are part of these
processes.
Example:
i. Products: Outcomes of a process activity
ii. Roles: Responsibilities of people involved in the process
iii. Pre- and post-conditions: Statements that are true before and after a process activity has
been enacted.
2. Describe the three generic software processes
Not definitive descriptions of software processes, they are abstractions of the process used to explain
different approaches to software development.
The waterfall model:
i. Plan-driven model: Separate and distinct phases of specification and development
Incremental development:
i. Specification, development, and validation are interleaved – may be plan-driven or agile.
Reuse-oriented software engineering:
i. System assembled from existing components, may be plan-driven or agile.
Most large systems use elements from all these models when in development.
, lOMoARcPSD|31863004
3. Outline the process activities of software requirement engineering, software development, testing and
evolution
Software specification: Process of establishing what services are required and constraints on the
system’s operation and development.
i. Feasibility Study: Is it technically and financially feasible to build the system?
ii. Requirements elicitation and analysis: What do the system stakeholders require or expect of
the system?
iii. Requirements specification: Defining detailed requirements
iv. Requirements validation: Checking validity of requirements
Software design and implementation: Process of converting the system specification into an executable
system
i. Software design: Design software structure realising the specification
ii. Implementation: Translate structures into an executable program.
Downloaded by Gabriel Musyoka (gabrielmusyoka940@gmail.com)
, lOMoARcPSD|31863004
Software validation: Verification and validation is intended to show a system confirms to its specification
and meets the customer requirements.
i. Involves checking and reviewing processes and system testing
ii. System testing involves executing the system with test cases that are derived from the
specification of real data to be processed.
iii. Stages:
Component testing: the components making up the system are tested by the people
developing the system.
System testing: System components are integrated to create a complete system.
Customer testing: This is the final stage in the testing process before the system is
accepted for operational use. The system is tested by the system customer (or potential
customer) rather than with simulated test data.
Software Evolution: Inherently flexible and can change. As requirements change through changing
business circumstances, the business support software must also evolve and change. Fewer and fewer
systems are completely new.
4. Why should processes be organised to cope with changes in the software requirements and design?
Change is inevitable in all large software projects
i. Business changes lead to new and changed system requirements
ii. New technologies open up new possibilities for improving implementations
iii. Changing platforms require application changes
Reducing costs of rework:
i. Change anticipation: Where the software process includes activities that can anticipate
possible changes before significant work is required.
ii. Change Tolerance: Where the process is designed so changes can be accommodated at
relatively low costs – Normally involves some form of incremental development.
Downloaded by Gabriel Musyoka (gabrielmusyoka940@gmail.com)
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through EFT, credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying this summary from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller gabrielmusyoka940. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy this summary for R46,96. You're not tied to anything after your purchase.
