order_44589_95694.docx - Running head SOFTWARE...

This preview shows page 1 - 3 out of 37 pages.

Running head: SOFTWARE ENGINEERING (ASSIGNMENT2) Software Engineering Assignment2 Names: Institution:
SOFTWARE ENGINEERING (ASSIGNMENT2) 2 Software Engineering Assignment2 Software engineering is the development process that aims at mitigating the cost of production of the high-quality software product. A software is a computer system that abstract and simulate activities of human beings. The software is not contained by material, or governed by physical laws or by the manufacturing process. As a result of this, the process of software engineering is simplified as there are no physical limitations on the potentiality of the software. On the contrary, the lack of natural constraints will imply that software can easily become extremely complex and thus very difficult to understand. The initial proposal of Software engineering took place in the year 1968 at the conference that was held to discuss the issues facing software developers. This software issues emanated directly from the onset of new computer hardware that was based on integrated circuits. The resultant software was large and more complicated than initial software systems. This assignment aims at testing the understanding of software engineering discipline. Question (a). Determine system requirement through requirement elicitation and workshops Requirement elicitation is the process of seeking, uncovering, acquiring, and elaborating requirements for computer-based systems [2]. Most importantly is to understand the requirements of a software system through elicitation rather than just capturing of collecting. This simply means that there exist discovery, emergence, and developments in the elicitation process. However, the process of requirement elicitation is complex and encompasses numerous undertaking and with the variety of available techniques, approaches, and tools for performing them. The strongholds and limitation of the process determine when each is appropriate for consideration of the context and situation. This question aims at giving a comprehensive survey of important aspects and understanding of the techniques and approaches used in the system requirement elicitations. Requirement elicitation (RE) is the learning and understanding the needs/wants of software users and project sponsors with the ultimate aim of communicating these needs to the system developers. The main goal of elicitation is to uncover, extract, and surfacing the want of the potential stakeholders. Requirement elicitation is trawling for the requirement to highlight the fact that thought this process you are likely to get more requirements than expected [4]. This means that gathering extraneous requirements initially is always better than gathering less. The following are the process of requirement elicitation Understanding the application domain. This process is important when beginning the process of requirements elicitation. It aims at investigating and examining the in details the situation in which the

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture