Sie sind auf Seite 1von 5

Personal Assignment 2

Week 2
Your name: Steven Andy Pascal
Answer all questions.
1. What are user requirements and system requirements?
2. What is the distinction between functional and non-functional
requirements?
3. List 3 types of non-functional requirement?
4. What is the software requirements document?
. !reate e"ample user requirement with topic system e-commerce or other
topic
#. !reate desi$n system for user requirement predeterminate with dia$ram
class % use case dia$ram% use case scenario.
Jawaban:
1.
& User requirements
' Statements in natural language plus diagrams of the services the
system provides and its operational constraints. Written for customers.
& System requirements
' A structured document setting out detailed descriptions of the
systems functions! services and operational constraints. "e#nes what
should be implemented so may be part of a contract between client
and contractor.
$.
& %unctional requirements
' Statements of services the system should provide! how the system
should react to particular inputs and how the system should behave in
particular situations.
' &ay state what the system should not do.
& 'on(functional requirements
' )onstraints on the services or functions o*ered by the system such as
timing constraints! constraints on the development process! standards!
etc.
' +ften apply to the system as a whole rather than individual features or
services.
,.
& -hese de#ne system properties and constraints e.g. reliability! response time
and storage requirements. )onstraints are ./+ device capability! system
representations! etc.
& 0rocess requirements may also be speci#ed mandating a particular ."1!
programming language or development method.
& 'on(functional requirements may be more critical than functional
requirements. .f these are not met! the system may be useless.
2.
Software requirements document is the o3cial statement of what is required
of the system developers. Should include both a de#nition of user
requirements and a speci#cation of the system requirements. .t is '+- a
design document. As far as possible! it should set of W4A- the system should
do rather than 4+W it should do it.
5.
-he #rst step in developing any e)ommerce application is to interview the
user base to generate a list of features to be included in the application. -his
comprises the important input for de#ning the capabilities of the application.
-here are two sets of users of shopping cart applications: site administrators
and end users who purchase items using their Web browsers. After
interviewing end users and administrators! application requirements such as
the following may be generated.
1nd User 6equirements
1nd user features that facilitate the en7oyment of .nternet shopping might
include the following:
Users should be able to use the e)ommerce application from any Web
browser supporting 4-&8 ,.$ 9or later: and coo;ies.
<isitors new to the site should be able to register by themselves. Users will be
di*erentiated by unique user identi#ers.
-ransactions should be secure. -hat is! a basic authentication mechanism
must be built into the application to prevent unauthori=ed persons from
ma;ing transactions on a user>s behalf. Secure soc;et layers 9SS8: or other
encryption mechanisms are typically used to thwart the access of sensitive
information 9such as credit card numbers: sent to the server by Web
browsers.
Site visitors should be able to purchase goods or services via the electronic
store.
Users should be able to view a complete list of speci#ed items available
through the site.
Users should be able to search for items by related attributes. %or e?ample!
visitors might search for )"s by artist! album title and/or genre or search for
boo;s by author! title and/or .S@' number.
Site visitors should be able to search the database using relevant ;eywords to
identify items of interest.
Users should be able to select items of interest and add them to their
shopping carts for future purchase.
<isitors should be able to modify the quantities of items in and/or delete
items from their shopping carts before chec;out.
All selected items should be shipped to the user following purchase.
Users should be able to view the status of items they have ordered.
8arge numbers of users should be able to use the application simultaneously.
-he performance of the application should not degrade with an increase in
the number of goods or services o*ered.
Administrator 6equirements
Administrators who manage the site have speci#c requirements of their own.
Administrators should be able to manage e)ommerce applications using Web
browsers.
"ata managers should be able to delete users.
Site administrators should be able to change the status of goods purchased
by users after items have been shipped.
Administrators should be able to view all user transactions.
Site managers should be able to view all transactions for the day.
A.

Das könnte Ihnen auch gefallen