Assignment

Read Complete Research Material

ASSIGNMENT

Assignment

Assignment

Part A

Elicitation is also called requirements discovery. It involves technical staff working with customers to find out about the application domain, the services that the system should provide and the system's operational constraints. May involve end-users, managers, engineers involved in maintenance, domain experts, trade unions, etc. These are called stakeholders (Helmer & Wong, 2003: 63). Example: Stakeholders in clinic software

Requirements elicitation is concerned with where software requirements come from and how the software engineer can collect them. It is the first stage in building an understanding of the problem the software is required to solve. It is fundamentally a human activity, and is where the stakeholders are identified and relationships established between the development team and the customer (Slagell, 2001: 14). This is very important as the requirement has all the information of the software and for validation and elicitation it is very necessary.

Example of communication relationships among actors and use cases in FRIEND (UML use case diagram). The Field Officer initiates the Report Emergency use case and the Dispatcher initiates the Open Incident and Allocate Resources use cases. Field Officers cannot directly open an incident or allocate resources on their own (Helmer, 2000: 45).

Example of use of extends relationship (UML use case diagram). Connection Down extends the Report Emergency use case. The Report Emergency use case becomes shorter and solely focused on emergency reporting.

Process automation does not only make everyday tasks more efficient--it saves your company money, as well. Freed from busy work, employees are able to focus on more productive tasks. And since the system keeps all important records in one place, there's no time or money lost dealing with misplaced or lost documents.

Some strategies have important implications for software architecture. Specifically, it is not just the software requirement specifications of the initial release that must be supported in the architecture. The software requirement specifications of early products need to be explicitly taken into consideration. Later releases are done through architectural qualities including extensibility and flexibility. The latter are expressed as non-software requirement specifications (Puketza & Zhang, 1996: 719). Use cases have become a widespread necessity for capturing software requirement specifications. This is the case in object-oriented projects.

Goals of good software design what is object oriented design? What is it all about? What are its benefits? What are its costs? It may seem silly to ask these questions in a day and age when virtually every software developer is using an object oriented language of some kind. Yet the question is important because, it seems to me, that most of us use those languages without knowing why, and without knowing how to get the most benefit out of them

a) The standards tree is intended for types of general interest to the Internet community. Registrations in the standards tree MUST be approved by the IESG and MUST correspond to a formal publication by a recognized standards body. In the case of registration for the IETF itself, the registration proposal MUST be published as an ...
Related Ads