Scribd
Upload
6 views16 pages

Lecture 6

E commerce lecture

Uploaded by

mccntnd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views16 pages

Lecture 6

E commerce lecture

Uploaded by

mccntnd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

E-Commerce Applications

Development

Software requirements
Software requirements
• Requirements are descriptions of services that a software
system must provide and the constraints under which it must
operate.

• Requirements can range from high level abstract statements


of services to detailed descriptions of individual module.
•
There are different types of requirements that should be
written down before development of any software/ product.

– Functional requirements.
– Non-functional requirements.
– User-requirements.
– System requirements.
Software requirements
Functional 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.
These requirements describe what the software does.

Describe functionality or system services.


Software requirements
Non- Functional requirements:

• Constraints on the services or functions offered by the system


such as timing constraints, constraints on the development
process, standards, etc

• Often apply to the system as a whole rather than individual


features or services.
Software requirements
Software requirements
User requirements:

• User requirements are written for customers in simple text


explaining about the system in easy manner.

• These are statements in natural language and along with


some diagrams , of what services the system is expected to
provide and constraints under it must operate.

• These are generally abstract.


Software requirements
System requirements:

• System requirements are written for developers.

• These are detailed descriptions about the system and they


include all the technical details to help the developers in
understanding system and development.
Beginnings of a Method

Requirements
Types of Diagrams
Types of Diagrams

• Structural Diagrams – focus on static aspects of the


software system
– Class, Object, Component, Deployment

• Behavioral Diagrams – focus on dynamic aspects of


the software system
– Use-case, Interaction, Activity
Structural Diagrams
• Class Diagram – set of classes and their
relationships. Describes interface to the class
(set of operations describing services)

• Object Diagram – set of objects (class


instances) and their relationships

• Component Diagram – logical groupings of


elements and their relationships
Behavioral Diagram
• Use Case Diagram – high-level behaviors of the
system, user goals, external entities: actors

• Sequence Diagram – focus on time ordering of


messages

• Activity Diagram – flow of control between


activities
Systems Activities

• The systems functionality is represented as a number of


Use Cases

• The functionality of each use case will be realised


through objects collaborating with each other

• Collaboration is achieved through message passing


Sequence Diagram for Placing
an Order
Customer Places Order
Description Order Customer Order Line Item Stock Item
Create Order .
Get Customer Details .
Insert order line .
item
Issue stock item .
Get order line .
cost
Get total order cost .
Order Customer Order Line Item Stock Item
Placing an Order
• A message is sent to the order class to create a
new “order”

– Customer No., Stock items and Quantities are


passed as parameters
– Customer details are retrieved from the appropriate
customer object
– For each stock item an order line object is created

• Details are extracted from the stock item object


Library Example
We have identified three objects: Borrower, Book and
Librarian and the following relationship:

Issuing a Loan

Triggered by a request from a Borrower for


the loan of a Book.

You might also like