in Core FC Package

tansygoobertownInternet και Εφαρμογές Web

8 Δεκ 2013 (πριν από 3 χρόνια και 8 μήνες)

64 εμφανίσεις

University of Southern California

Center for Systems and Software Engineering

Common mistakes

in Core FC Package

October 15, 2010

University of Southern California

Center for Systems and Software Engineering

Outline


OCD


PRO


SSAD


LCP


FED

University of Southern California

Center for Systems and Software Engineering

Operational Concept Description


Benefit Chain Diagram


How each stakeholder create
benefit
, especially in
operation phase
?


Should correspond to your organization goals and core capabilities


Element Relationship Diagram


What are the elements that
you develop
(put them in dashed box) ?


What are the elements that
you have to coordinate
/ interoperate (put
them outside the dashed box)?


Business Workflow


Sequence of
works
that
stakeholders
have to perform


Will reflect on how your new system
improve the current workflow


Do not care about how your system works (
not a technical flow
)

University of Southern California

Center for Systems and Software Engineering

A not so good Benefit Chain Diagram

Common Mistakes

-
Focus too much on what
you develop

-
Missing critical
stakeholder

-
Missing core initiatives

-
Missing contributions

-
Wrong notations

-
Initiative and outcome
don’t match

Overemphasized

Underemphasized

University of Southern California

Center for Systems and Software Engineering

A Good example of Benefit Chain Diagram

Assumptions
:
-

Stable networking platform
-

Sufficient web
-
server’s
(
hardware
)
resources to
cupport concurrent access of more than
1800
students
-

Sufficient bandwidth to support concurrently
access of students
-

Database grow over the time
,
correponding
tunning and indexing
Simplified Registration
and Peer Review
Process Management
Student
,
Faculty
&
Administrator
Develop Online Peer
Review Management
System
Register online to access
peer review system
Faster peer review
process management
Developers
and IV
&
V
Student
Submit portfolios
Faster registration
and validation
Faster and easier
essay submissions
Administrator
Provide submission
deadlines and trigger
reminders to faculty for
prompt submission
Faculty
Provide essay prompts
and trigger reminders to
students for essay
submission
Easier tracking of
prompt submissions
Easier tracking of
essay submissions
Faster essay allocation
&
review
;
Saving of
individual effort
Faster essay
allocation
,
reviews
and processing
Administrator
,
Faculty
Access essay repository
for reference
Generate reports for
analysis
Student
,
Faculty
&
Administrator
Critique
,
Review and
Grade Essays
Improve writing skills of
students and effort for all
Increase Productivity
and Enhance reputation
of Writing Program
Improved
productivity
and peer
management
Easier management
and retrieval of essays
Easier statistic and
report management
Maintainer
Provide training to new
users and maintain
current system
Easier management of
system
Contribution
Initiative
Outcome
Stakeholder
University of Southern California

Center for Systems and Software Engineering

A not so good example of
Element Relationship Diagram

User

A
U
T
H
E
N
T
I
C
A
T
I
O
N

Stage
Manager


Editor/D
esigner


Show
Roster


Administ
rator


Budget Data


Scheduling
Data

D
at
ab
as
e


M
an
ag
e
m
en
t


Sy
st
e
m

Tas
ks

Database

Reporting


Task Tracker


Project
Operation
s


Activate
s

Contro
ls

Uses

Uses

Creates report using
budget data

Tracked
using


Username
/
Password


Visitor

Requests for
access


Creates and manages
show

Manages designer tasks


View schedule and
tasks


Creates Show, Budget
manages user account


Common Mistakes

-

Unorganized drawing

-
Mixing between the
module you develop and
module you link to

-

missing elements that
you link with

University of Southern California

Center for Systems and Software Engineering

A good example of Element
Relationship Diagram

University of Southern California

Center for Systems and Software Engineering

A not so good example

Visit website homepage

Already a
member?

Log
-
in

Sign
-
up

no

yes

Access training videos and material,
Provide feedback, securely download
material, Access the discussion board,
Online shopping, Access coupons

User

System

Common Mistakes

-

Focus on technical flow

-

Too detail on system’s
behavior instead of
“business” transaction

University of Southern California

Center for Systems and Software Engineering

A good example of

Business

Workflow Diagram

University of Southern California

Center for Systems and Software Engineering

Prototype


Critical issues and concerns are not stated


State the specifics of each


Be specific to what prototypes are to address


Only UI is not sufficient


If UI is the only concern, then OK


Otherwise, discuss about how you meet the
capabilities or level of service


University of Southern California

Center for Systems and Software Engineering

SSAD


Generally good in translating the OOA&D
concepts into analysis


Some misunderstanding in conceptual
separations of different diagrams/models

University of Southern California

Center for Systems and Software Engineering

System Context Diagram


Incorrect hierarchy of actor classes


Should match exactly with the use
-
case model


Look for common functionalities


Incorrect system scope


What you are developing


External systems


Not an actor


Show as another system/component

University of Southern California

Center for Systems and Software Engineering

Artifacts and Information


Many components are not artifacts


Association = sharing of information


Persistent data that are stored/used by system
for execution


Think in terms of database design.


The information architecture of the system

Artifacts/Information

ARE

Artifacts/Information are NOT

User profile

User

Reports

System

Application form

University of Southern California

Center for Systems and Software Engineering

Use
-
Case


Hierarchy of users


Look for common use
-
cases


Missing related capability requirements/win
conditions


Incorrect pre
-
/post
-

conditions


Course of actions not shown in sequence


Missing actors described in the system context


University of Southern California

Center for Systems and Software Engineering

Pre
-
/Post
-

Conditions

Bad precondition:


“User wants to access the website”


“User needs to provide valid information”

Good precondition:


“User is Administrator. Database is initialized”


Bad postcondition:


“Information was changed”

Good postcondition:


“User information is saved to the database.”


“If username and password are verified, user is
granted access; otherwise, user is denied access.”

University of Southern California

Center for Systems and Software Engineering

Course of Actions

Good

Bad

#

Actor’s Actions

System’s Response

1

[User] Enters the
payment amount

2

[User] Clicks
“Donate”

3

Sends information to
Paypal and redirects
to Paypal

4

[Paypal] Generates
confirmation

5

Receives
confirmation from
Paypal

6

Displays message
“Donation complete”

#

Actor’s Actions

System’s
Response

1

[User] Enters the
payment amount and
clicks “Donate”

Sends information to
Paypal and redirects
to Paypal

2

[Paypal] Generates
confirmation

Receives
confirmation from
Paypal and displays
confirm message

University of Southern California

Center for Systems and Software Engineering

Use
-
Case

Bad

Good

University of Southern California

Center for Systems and Software Engineering

FED


4.2.1 NDI/NCS Candidates


For each functionality you are looking for in
NDI/NCS, you should evaluate more than 1
product


4.2.2 NDI/NCS Evaluation Criteria


Trace back with OCD for Capability Goals and
LOS Goals

University of Southern California

Center for Systems and Software Engineering

4.2.1 NDI/NCS Candidates


Think about what are available in the market


List the possible candidates (more than one)


Prove by using
4.2.2 criteria
and show results
in
4.2.3 results
which your choice is the best

University of Southern California

Center for Systems and Software Engineering

For example: you are looking for
one or more
NDI/NCS that has the following functionalities


content management system


an online calendar tool


Example:

NDI/NCS products

Rationale

Content Management System

1. Joomla

<< explain rationale>>

2. Drupal

<< explain rationale>>

3. Moodule

<< explain rationale>>

An online calendar tool

1. Google Calendar

<< explain rationale>>

2. LiteCalendar

<< explain rationale>>

3. XLCalendar

<< explain rationale>>

University of Southern California

Center for Systems and Software Engineering

4.2.2 NDI/NCS Evaluation Criteria


One table for the attributes


Check ICM EPG for common attribute


Check your OCD for LOS goals


Example: Concurrency, 24/7 availability, interoperability


At least one table for the features


Check your OCD for capability goals


Elaborate Capability Goals into features or sub features


Could separate into many tables for different Capability,
e.g. one table for CMS, one table for online calendar tool


You will later use table of attributes and table of
features as a scoring guide in 4.2.3

University of Southern California

Center for Systems and Software Engineering

Example of table of features

No.

Features

Score

CMS1

Publishing web pages

30

CMS2

Discussion board

15

CMS3

User Profiles

10

CMS4

Various authorization level

10

CMS5

Blog

25

CMS 6

Users statistics

10

Total

100

Features for the Content Management system

No.

Features

Score

CAL1

Add / update / delete event

50

CAL2

Add / update / delete photo

10

CAL3

Synchronization with mobile phone

10

CAL4

Email reminder

30

Total

100

Features for the Content Management system