Tom Kelliher, CS 319
Sept. 4, 1998
Announcements: Brooks book? Leaning toward client/contractor project
From last time:
- Waterfall, evolutionary development models.
Assignment: Read Chapter 2.
- Increasing dependence upon complex software. Increasing percentage
of GDP. Consequences?
- Generic, bespoke systems. Examples, differences.
- Software product attributes: maintainable, dependable,
appropriately efficient, usable.
- Software process composed of activities and deliverables:
- Software specification.
- Software development.
- Software validation.
- Software evolution.
- Waterfall model, evolutionary development.
- Exploratory programming: ``Ready, fire, aim.'' Get something
working. Modify until ``acceptable.''
- Prototyping: Get something working. Create a requirements
specification. Develop the ``real'' system.
- Formal translation: Get a formal specification.
- Code reuse: Use COTS software to build the system.
- Why do managers like this model?
- What are its drawbacks?
- Exploratory programming, throw-away prototyping.
- Evolutionary development appropriate for?
- What is risk in software engineering?
- Consider risk in a radiation treatment system.
- Consider risk in an online system for accessing student advising,
- Describe the process model you utilized in your last programming
- What is the most appropriate generic software process model for
developing each of the following systems:
What risks might be involved in each of these?
- An automotive ABS system.
- A software maintenance VR system.
- A college accounting system designed to replace an existing
- An interactive system allowing railway passengers to find train
times from terminals installed in the station.
- A university intends to procure an integrated student management
system. The alternative approaches to be adopted are either:
Are there other possible alternatives? Identify two possible risks in each
of these strategies and suggest techniques for risk resolution which would
help in deciding which approach to adopt.
- Buy a DBMS and develop a system in-house.
- Buy a system from another university and modify it.
- Join a consortium of other universities, establish a common set of
requirements and contract a software house to develop a single system
for all members of the consortium.
- Should professional societies have codes of conduct? Should
disciplines have professional societies?
Thomas P. Kelliher
Thu Sep 3 08:47:34 EDT 1998