Transcript Document 7601364

Marvel Electronics Inc.
Team 1
Amit Nimse
M Rajaul K Khan
Shasank Bhandari
Tonda Phillips
Vikram Sitaram
Kumar Unnikrishnan
Instructor:
Dr. Lawrence Chung
AGENDA
Describing the requirement process followed
for e-store project
Outcomes of requirement process
Addressing issues of the Standish report
Questions and Answers
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
2
User Requirement
Build a tower as tall as possible.
Time limit of 10 minutes.
Make it rigid.
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
3
Requirement in action
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
4
User Testing
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
5
Final Result…
Standish Report still prevails !!!!!
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
6
Team Architecture
Project
management
Amit Nimse
M Rajaul K Khan
Modeling
√
√
√
√
√
√
√
Vikram Sitaram
Mock-up development
√
√
Shasank Bhandari
Tonda Phillips
Requirement
Engineering
√
Kumar Unnikrishnan
√
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
√
7
Process Flow
Business Driver
Users
Inception
Specification
Validation
Elicitation
Problem Domain
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
8
Actigram for Process
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
9
Inception Phase.
Steps Undertaken:
 Understanding Background and Problem
Definition of e-store project.
 Studying business objectives for the estore project.
 Analyzing scope of the project and
feasibility of implementation.
.
.
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
10
Elicitation Phase
Steps Undertaken:
Identifying Users and Stakeholders.
Participating in Brainstorming Session.
Identifying and Prioritizing Wants and
Needs.
Generating Vision Document.
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
11
Specification
Steps Undertaken:
• Generate Business Models.
• Functional and Non functional models for Software
system.
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
12
Business Models
Steps Undertaken:
 Identifying business actors, business entities and business workers
in the current business of Marvel Electronics.
 To depict the “To-Be” business model …




Business use case diagram.
Business class diagram.
Business activity diagram.
Business sequence diagram.
 Identify different entities that are going to interact with the e-store.
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
13
Business Model
Business Use Case Diagram.
Marvel Electronics and
Home entertainment
Business use case
diagram
<<include>>
Buy Products at Retail Store
<<include>>
Customer
Buy Products Online
Purchase
<<include>>
billPaySystem
Use Financing options
Novice User
configure Products Online.
Technical User
Use customer support service
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
14
Business Model
Business class diagram.
Business Class
Diagram
Order
1..*
invoice
1..*
Sales
creditCard
1
1
SupportCase
1
1
1
e-store
1
shoppingCart
1
accounting
CRM
contentManagement
5/25/2016
configurableServices
commonRegistration
CS 6361- Requirements Engineering - Course
Project.
exportRegulation
15
e-store
contentManagement
Sales
creditManagement
billPay
shipping
Business activity diagram for
purchase products online
Browse
Provide Product
information
Buy
Products
cart : shoppingCart
[Create]
Pay Online
[ Retry ]
checkCredit
authorize
payment
: shoppingCart
[ authorization failed ]
: creditCard
[ Cancel ]
Cancel
Transaction
[ authorization success ]
myCart : shoppingCart
[destroyed]
create
invoice
Create
Order
: invoice
New order
for shipping
myOrder : Order
[Created]
5/25/2016
Notify
Customer
CS 6361- Requirements Engineering - Course
Project.
16
Business Model
Business Sequence Diagram (Purchase Product).
: Customer
: e-store
1: browseProducts
: contentManager
: creditManager
: paymentAuthorizer
: salesRep
: shippingManager
2: getProductDetails
3: purchase
4: checkCredit
5: authorizePayment
6: createInvoice
7: createOrder
8: notify
9: notify
5/25/2016
Business Sequence diagram for
purchase products online
CS 6361- Requirements Engineering - Course
Project.
17
Business Model
Business Sequence Diagram (Configure Product).
business sequence
diagram for
configure produ...
: Customer
: e-store
: configurator
1: configureProduct
2: validateConfiguration
3:
4:
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
18
E-store System Functional Model
Steps Undertaken:
Use case analysis for e-store system.
Creating Structural Requirements model
using class diagram.
Creating Behavioral Requirements model
using sequence diagram and activity
diagram.
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
19
E-store functional model
Use Case diagram.
e-store use case diagram
Configure Products
configurator
<<include>>
Provide Product Reviews
and Ratings
contentManager
Display Product Offerings
Customer
Search Products
SalesRep
Provide Support
commonRegistrati
on
<<include>>
<<include>>
Maintain Customers
<<include>>
Track Shipments
Offer financing
<<include>>
Order Management
<<include>>
<<include>>
Process Payment
paymentAuthorizer
Purchase Products
<<include>>
Calculate Tax
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
20
E-store functional model
Class Diagram.
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
21
E-store functional model
High level Sequence diagram.
: e-store
: Customer
1: register( )
2: searchProduct( )
3: configureProduct
4: purchaseOnline
5: usefinancingOptions
6: requestSupport( )
5/25/2016
CS 6361- Requirements Engineering - Course
High level sequence
Project.
diagram
22
E-store functional model
Sequence diagram (Purchase Product).
: e-store
: Customer
:
paymentAuth...
1: checkoutCart( )
2: authenticateCustomer( )
3: selectPaymentMethod( )
4: selectShippingMethod( )
5: authorizePayment
6: confirm Payment
7: confirmOrder
sequence diagram for purchase
product
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
23
E-store functional model
Sequence diagram (Configure Product).
: Customer
: e-store
: configurator
1: selectProductToConfigure( )
2: getComponents
3:
4: selectComponent( )
5: commitConfiguration( )
sequence diagram for
configure products online
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
24
E-store functional model.
Sequence diagram (Display product offerings).
: Customer
: e-store
:
contentManager
1: showProductDetails( )
2: getProductDetails
3: showProductReviews( )
4: getProductReviews
sequence diagram for display
product offerings
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
25
E-store Nonfunctional Model
Nonfunctional requirements identified in
our e-store system:
Security *(6.1 – 6.3)
Usability *(6.4)
Availability *(6.5 , 9.2)
SIG is used to model above mentioned
Nonfunctional requirements.
[* Reference from Vision Document]
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
26
E-store Nonfunctional Model
SIG (Security)



Security

Data Storage
Data Transfer



5/25/2016


Secure
Sockets
Secure
Session


CS 6361- Requirements Engineering - Course
Project.
Confidentiality

27
E-store Nonfunctional Model
SIG (Security Cont…)
Secure Session (cont.)



Session
Timeouts


5/25/2016
Automatic
Logoff




Confirm
Transactions
Secure
Cookies


Leave NO
Passwords
CS 6361- Requirements Engineering - Course
Project.


Leave NO
Personal
Data
28
E-store Nonfunctional Model
SIG (Security Cont…)
Confidentiality (cont.)



Browsers

Back-end
Servers







5/25/2016
Passwords
Never
Displayed
Logoff

Credit Card
Number retrieved
as last 4 digits
only

Passwords never
displayed,
only re-settable
CS 6361- Requirements Engineering - Course
Project.

Restricted
Access to
authenticated
Administrators

Encrypted
Database
29
Validation Phase
Communicating requirements models to
stakeholders.
Using mock-ups to validate the
requirements.
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
30
Mock–ups Screen (Home Page)
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
31
Mock–ups Screen (Create Account)
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
32
Mock–ups Screen (After Logged-in )
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
33
Mock–ups Screen (Product View)
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
34
Mock–ups Screen (Configure Product)
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
35
Mock–ups Screen (Credit Card Payment )
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
36
Mock–ups Screen (View Order)
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
37
Mock–ups Screen (Tracking Order)
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
38
Addressing issues in Standish Report.
 Incomplete
Requirements
 Changing
Requirements
 Lack of user
involvement
5/25/2016
 Addressed by user
interaction and
Traceability
 Addressed by
Traceability
 Addressed by user
interaction and Mockups
CS 6361- Requirements Engineering - Course
Project.
39
Traceability
Traceability Hierarchy
Stakeholder Need
traces
Product Feature
Supplementary Requirements
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
Use Case
40
Sample Traceability
Brainstorming Session
Vision Document
Use case diagram
5/25/2016
Traceability matrix
CS 6361- Requirements Engineering - Course
Project.
41
Traceability
A Traceability Matrix is used to trace
requirements.
An element in a row that maps to an
element in a column is marked by a ‘X’ at
the intersection of that particular row and
that particular column.
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
42
Traceability
The Traceability Matrices
 User Needs - Features
 Features - Use Cases
 User Needs – Constraints
Traceability Matrix
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
43
Next steps
Refine Nonfunctional SIG models.
Finalize project deliverables.
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
44
Conclusion
Learning Objectives achieved specify and follow a requirements engineering process –











5/25/2016
to identify stakeholders (and other sources of requirements), elicit their needs and
objectives, identifying and resolving conflicts.
to differentiate process requirements from product requirements
to manage changing requirements
to model structural, behavioral and non-functional requirements
to understand the derivation of architectural and design models from requirements
specification
to validate requirements
to build a mock-up
to establish requirements traceability
to use a CASE or modeling tools to capture the requirements
to produce a clear, comprehensive and complete Software Requirements Specification
to understand the whys, what's and how's of a software system
CS 6361- Requirements Engineering - Course
Project.
45
Q&A
?
??
???
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
46
Thank You
5/25/2016
CS 6361- Requirements Engineering - Course
Project.
47