TAILIEUCHUNG - Software Engineering For Students: A Programming Approach Part 8

Software Engineering For Students: A Programming Approach Part 8. This fully revised version of Doug Bell's Software Engineering: A Programming Approach continues to use the successful formula of the previous editions. The author's approach is to present the main principles, techniques and tools used in software engineering, one by one, chapter by chapter. This book is a unique introduction to software engineering for all students of computer science and its related disciplines. It is also ideal for practitioners wishing to remain current with new developments in the area | 48 Chapter 4 Requirements engineering Appendix A gives specifications for several systems. For each specification identify any problems with the specification such as ambiguities inconsistencies and vagueness. Group exercise. One way of understanding more clearly the difficulties of carrying out requirements elicitation is to carry out a role-playing exercise. Students can split up into groups of four people in which two act as users or clients while the other two act as software analysts. The users spend ten minutes in deciding together what they want. Meanwhile the analysts spend the ten minutes deciding how they are going to go about eliciting the requirements from the users. The users and analysts then spend 15 minutes together during which the analysts try to elicit requirements. At the end of this period an attempt is made to get all parties to sign the requirements specification. After the role play is complete everyone discusses what has been learned from the exercise. Possible scenarios are the systems already specified in Appendix A. Requirements specifications are sometimes very long - they can be as long as a book. Suggest a software tool that could be used in addition to a word processor to assist in writing checking browsing and maintaining a specification. Consider for example using a web browser and including hyperlinks in a specification to promote cross-referencing. Who should be consulted when collecting the requirements of a computer-based system to replace an existing information system Who should be consulted when collecting the requirements for a process control system or an embedded system It is not immediately obvious who the users of these systems will be. Define the terms completeness and consistency in a specification. How can we achieve them What are the skills required to collect analyze and record software requirements Explain the difficulties in using natural language for describing requirements.