Information Technology Reference
In-Depth Information
13.8 Chapter Summary and Conclusions
There is more to software development than coding; proper design and testing
along with an emphasis on strong deliverables is essential to a successful project.
The Software Development Life Cycle (SDLC):
• Planning
• Analysis
• Design
• Implementation
• Maintenance
Different stakeholders and end users have different needs. It is the job of the
software engineer to accommodate each user type with appropriate documentation
and systems capability. Software specification comes in both written and illus-
trative types. Both types have merits.
• Written documentation: verbose, complex and detailed.
• Illustrative: more understandable at a glance and less verbose.
A learning exercise has to have an objective and a way to measure the level of
success that was achieved when attempting to reach this objective. One way to
measure success is by an honest evaluation by peers. Peer evaluations should have
the following traits:
• Peers should be in an environment where they can honestly assess themselves
and their peers without being biased.
• Peer evaluations should provide relevant questions to the phase of development.
• An overall evaluation should be performed to determine the amount of personal
growth.
13.9 Exercises
1. How many times should peer reviews be completed?
2. Name and explain two differences between Gantt and N
2
.
3. Explain the importance of benchmarks.
4. Name and differentiate between the two main types of benchmarks.
5. Complete a mock demonstration of any existing software product as if you
had developed it.
6. What are the main tenants of the Software Engineering ethics listed in this
chapter?
7. What should be delivered at the project's completion?
8. What are the traits of a successful team? Name a trait that you think is
important that is not listed in this chapter.
