SOFTWARE ENGINEERING assignment 4 - Essay Example

Software Assignment 4 Answer to section 7 The term stakeholder is used to refer to any person or group who will be affected by the system, directly or indirectly. In a university student records system the stakeholders are as follows:On the university front:1. Firstly, the staff responsible for handling the entire system on the behalf of the university. They know what actually happens when a system variable or process is required to be altered.2. Secondly, the university officials who have asked for its creation.

They know what is getting done.On the developer's front:1. The software engineers, business managers and domain experts. Stakeholders often do not understand what they exactly require form the computer system. They end up naturally expressing requirements which they think should be taken care first. They end up expressing their thoughts on one topic and end up getting confused with their own ideas. The requirements of several stakeholders will always conflict as they are very natural. The end user's view of the process implementation is differently perceived from the viewpoint of the managers and way different from the developers.

The reason being that every stakeholder wants his/her version of the logic to be a system. To some, one thing could be different form another, to someone else. They precisely have different set of requirements which help them to conceptualize what they think is true. Answer to section 7.9The point when emergency changes have to be made to systems they can be modified in the requirements document using a suitable process model. The model to be employed is the spiral model. The process activities involved in maintaining the consistency between the requirements document and the system implementation are:Requirements discovery: Here collection of requirements and documentation is discovered.

Requirements documentation: The requirements are documented at this stage.The requirements are discovered at the first stage and as it is a spiral model it spirals itself and prioritizes the requirements, implements it and documents it in the cycle it covers.The spiral model is best to be used as it keeps on circling and thereby steps in all the phases of software development life cycle including system implementation and requirements documentation gets implemented. It makes the system consistent by circling every time a change takes place in the software and traveling all the phases so as to make it organized and complete.

It is the best model to accommodate the changes in the business environment and document it for future reference. ReferencesSommerville, Ian. Software Engineering. PearsonEducation, 2004.