Professional Documents
Culture Documents
SILABUS
W|I|N|D|U
Tujuan :
Mengenalkan dan
menggunakan berbagai
model pengembangan
sistem perangkat lunak,
analisa terstruktur,
analisa berorientasi objek,
serta testing dan
implementasi
N
o
1.
2.
Target :
Pemula dan Menengah
Peralatan :
Komputer dengan Sistem
Operasi Windows atau
Linux
Netbeans 6.5
Sparx Enterise Architect
Redmine Project
Management
3.
4.
Materi
Tujuan
Keterangan
Analisa Terstruktur
a.
DFD (Data Flow Diagram)
b.
ERD (Entity Relation Diagram)
c.
LRS (Logical Structure
Record)
d.
Flowchart
e.
Workflow
Peserta dapat
mengenal dan
menggunakan
berbagai model
pengembangan
sistem perangkat
lunak
Peserta dapat
mengenal dan
menggunakan
analisa terstruktur
Peserta dapat
mengenal dan
menggunakan UML
(Unified Modeling
Languange)
Peserta dapat
mengenal dan
menggunakan cara
melakukan testing
dan implementasi
serta aplikasi
project
management
W|I|N|D|U
Technological Obsolescence
Water Fall
SDLC
Spiral
Prototype
RAD
Agile
W|I|N|D|U
Technological Obsolescence
W|I|N|D|U
Water Fall
W|I|N|D|U
Water Fall
W|I|N|D|U
Development Process
SAVILLA
7
W|I|N|D|U
Water Fall
W|I|N|D|U
Feasibility Study
A definition of the problem
Determination of technical and
economic viability
Alternative solutions and their expected
benefits
Required resources, costs, and delivery
dates in each proposed alternative
solution
Software Engineering and Testing
By B. B. Agarwal, S. P. Tayal, M.
Gupta
W|I|N|D|U
10
W|I|N|D|U
11
W|I|N|D|U
12
W|I|N|D|U
13
W|I|N|D|U
Maintenenance
The set of activities that are performed after the system is delivered to the
customer.
Consists of correcting any remaining errors in the system (corrective
maintenance), adapting the application to changes in the environment
(adaptive maintenance), and improving, changing, or adding features and
qualities to the application (perfective maintenance).
60% from costs
20% Corrective and Adaptive Maintenance
50% Perfective Maintenance
14
W|I|N|D|U
MAINTENANCE
Corrective Maintenance Activities
triggered by software faults encountered during the use of the software.
Software Engineering
By Kassem A. Saleh
15
W|I|N|D|U
Software Developmet
Life Cycle( SDLC)
The System
Develoment Life
Cycle (SDLC) model,
also called the
waterfall model, is
one of the most
popular development
models used in the
software industry. The
origin version of this
model was presented
by Wiston Royce In
1970.
Systems Analysis and Design
By Gary Shelly, Harry J. Rosenblatt
16
W|I|N|D|U
SDLC Phases
17
W|I|N|D|U
Spiral
http://www.maxwideman.com/papers/linearity/spiral.htm
Reliable Systems
18
W|I|N|D|U
Prototyping
http://www.enggpedia.com/answers/2057/advantage
s-prototype-software-development-instead-waterfall
FUNDAMENTALS OF SOFTWARE
ENGINEERING
By RAJIB MALL
19
W|I|N|D|U
20
W|I|N|D|U
Agile Development
(2000)
Individuals and
Interactions over
processes and tools
Working software
over comprehensive
documentation
Customer
Colaburation
Responding to
change over
following a plan
21
W|I|N|D|U
Extreme Programming
http://www.extremeprogramming.org/map/project.html
22
W|I|N|D|U
Extreme Programming
- pair programming : accelerates the
excange of knowledge between
developers, between developer and
testers, ang generally with the team.
- An on-site customer : is available for
questions with regard to the
requiements at any ime, and takes
decisions in this respect. together with
the tester, the on-site customer
prepares funtioal tests, which can also
be used for acceptance tests later on.
- Continuous Integration : ensures
that small steps help minimize the risk
of changes, and walks thrverify that the
entier system through all tests to
cotinuously verify that the entire
system is faultless
Web.Engineering.The.Discipline.of.Systematic.Development.of.Web.Appli
cations.Jul.2006.
John.Wiley.and.Sons.
23
Extreme Programming Pocket Guide By Chromatic
W|I|N|D|U
SCRUM
Scrum is a management framework for incremental product development
using one or more cross-functional, self-organizing teams of about seven
people each.
It provides a structure of roles, meetings, rules, and artifacts. Teams are
responsible for creating and adapting their processes within this framework.
Scrum uses fixed-length iterations, called Sprints, which are typically two
weeks or 30 days long. Scrum teams attempt to build a potentially
shippable (properly tested) product increment every iteration.
24
W|I|N|D|U
Scrum Master
http://scrumtrainingseries.com/Intro_to_Scrum/Intro_to_Sc
rum.htm
25
W|I|N|D|U
26
W|I|N|D|U
27
W|I|N|D|U
28
W|I|N|D|U
W|I|N|D|U
Campaign
Manager
Client name +
Campaign name
Budget surplus
Budget
Campaigns
30
2.4
Check
Campaign
Budget
Cost
Adverts
W|I|N|D|U
Elements of DFDs
External Entities
People, organizations or systems that
the system being modelled
communicates with
Rather like actors, except an external
entity is not necessarily a direct user of
the system
Campaign
Typically trigger processes
Manager
31
W|I|N|D|U
Elements of DFDs
Processes
Processes that transform data
in some way
Named and numbered
Normally require at least one
input and produce at least one
output
Inputs / outputs (I/O) may flow
to or from other processes,
data stores or external entities
2.4
Check
Campaign
Budget
32
W|I|N|D|U
Elements of DFDs
Data Stores
Represent the places where data is
stored
Typically files or database tables
In a manual system can represent
physical data stores, like card indexes or
filing systems
Campaigns
33
W|I|N|D|U
Elements of DFDs
Data Flows
Flows of data between:
external entities and processes
processes and other processes
processes and data stores
34
W|I|N|D|U
Data Dictionaries
W|I|N|D|U
Levels of DFDs
Context Diagram
Shows the system and the external
entities with which it interacts
36
Context Diagram
W|I|N|D|U
Staff Assignment
Campaign
Manager
Payment
Accountant
Campaign
Staff
Client
Budget
Agate
Campaign
Management
System
Staff Grade
Advert Completion
Client Contact
Staff
Contact
Advert
Campaign
Staff
Concept Note
Concept Note
Staff
37
W|I|N|D|U
Client
Campaign
Manager
Staff
Clients
1.
Record
Clients
Staff
Client
4.
Maintain
Staff
Staff Grade
Staff Members
Staff Assignment
Payment
Staff
Campaign
Budget
Accountant
Staff
2.
Plan and
Manage
Campaigns
Campaigns
Concept Note
Campaign
Contact
Cost + Completion Date
5.
Manage
Adverts
Staff
Contact
Client Contact
Adverts
Advert
Campaign
Staff
Advert Completion
3.
Prepare
Adverts
Advert
6.
Browse
Concept
Notes
Concept Note
Notes
Concept
Note
Staff
Concept
Note
38
Level 1 Diagram
W|I|N|D|U
Staff Members
Client Contact
Staff
5.1
Set Client
Contact
Contact
Adverts
Advert Completion
5.2
Set Advert
Completed
Completion Date
39
W|I|N|D|U
Data Dictionary
40
W|I|N|D|U
Data Dictionary
41
W|I|N|D|U
Process Definition
W|I|N|D|U
Types of DFD
W|I|N|D|U
W|I|N|D|U
45
W|I|N|D|U
Variations in Notation
46
SADT
W|I|N|D|U
Campaign
Manager
Client name +
Campaign name
Budget surplus
Budget
Campaigns
2.4
Check
Campaign
Budget
Cost
Adverts
47
SSADM
W|I|N|D|U
Campaign
Manager
Client name +
Campaign name
2.4
Check
Campaign
Budget
Budget surplus
Budget
D1 Campaigns
Cost
D2 Adverts
48
W|I|N|D|U
SSADM
49
W|I|N|D|U
50
W|I|N|D|U
Summary
51
W|I|N|D|U
References
Yourdon (1989)
Skidmore, Mills and Farmer (1994)
(For full bibliographic details, see Bennett,
McRobb and Farmer)
52
W|I|N|D|U
Entity
Technology
53
W|I|N|D|U
54
W|I|N|D|U
55
W|I|N|D|U
Chen
Entity
Relationship
Atribut (Identifier)
1 : 1
1 : N
N : M
Cardinality
56
W|I|N|D|U
W|I|N|D|U
1 to 1
Chen
A
Information Engineering
A
A1
58
W|I|N|D|U
Weak Entity
A Weak entity is introduced into ER
Diagram (Chen), it indicates that the
relationship between that entity and at
least one of its parents is mandatory.
59
W|I|N|D|U
1 to M (Chen)
Customer_last_name
Customer_first_name
Customer_street
Order_numb
Customer_number
Customer_city
Customer_state
CUSTOMER
D
o
ORDER
Order_date
Credit_exp_date
Customer_zip
Order_filled
Customer_phone
Credit_card_numb
60
W|I|N|D|U
1 to M (IE/Martin)
61
W|I|N|D|U
CUSTOMER
1
ACTOR
D
o
Ha
s
Sup
ply
M
ORDER
M
Co
nt
ain
ITEM
PRODUCER
Has
62
W|I|N|D|U
63
W|I|N|D|U
DISTRIBUTOR
customer_numb
CUSTOMER
(pk)
distributor_numb
customer_first_nam
(pk)
e
distributor_name
customer_last_nam
distributor_street
e
distributor_city
customer_street
distributor_state
customer_city
distributor_zip
customer_state
distributor_phone
customer_zip
distributor_contact
customer_phone
contact_person_ext
credit_card_num
card_exp_date
ORDER
ITEM
order_numb
item_numb
customer_numb
title
(fk)
distributor_numb
order_date
(fk)
order_filled
retail_price
release_date
Database Analysis and Design
genre
by I. T. Hawryszkiewycz
ACTOR
actor_numb
(pk)
actor_name
HASACTOR
actor_numb (pk)(fk)
item_numb (pk)(fk)
description
HASPRODUCER
producer_name (pk)
(fk)
Item_numb (pk)(fk)
description
PRODUCER
producer_name
(pk)
studio
64
W|I|N|D|U
Flowchart
Flowchart
https://www.cs.ucy.ac.cy/~nicolast/courses/cs654/lectures/Flow
65
charting.pdf
W|I|N|D|U
Flow Chart
66
W|I|N|D|U
Flowchart
67
W|I|N|D|U
Workflow
68
W|I|N|D|U
Workflow
69
W|I|N|D|U
Workflow
70
W|I|N|D|U
Workflow
71
W|I|N|D|U
Workflow
72
W|I|N|D|U
73
W|I|N|D|U
Modeling Application
W|I|N|D|U
Modeling Applications
FUNDAMENTAL
(Software Engineering)
W|I|N|D|U
Modeling
Modeling Applications
Specifics in Engineering
W|I|N|D|U
Modeling Applications
W|I|N|D|U
Actor
Use Case
Association Relationship
Include Relationship
Extend Relationship
Generalization
Relationship
<<includes>>
<<extends>>
78
W|I|N|D|U
W|I|N|D|U
W|I|N|D|U
Multiplicity
Unspecified
Exactly One
Zero or More
0..*
Zero or More
One or More
1..*
0..1
Specified Range
2..4
2, 4..6
81
W|I|N|D|U
W|I|N|D|U
W|I|N|D|U
W|I|N|D|U
What Is a Sequence
Diagram?
Sequence Diagram
85
W|I|N|D|U
W|I|N|D|U
W|I|N|D|U
Black Box
White Box
Web Project Management
88
W|I|N|D|U
Software Testing
By Milind G. Limaye
89
W|I|N|D|U
Black Box
Requireme
nt
Input
BLACK BOX
Output
Events
90
W|I|N|D|U
Black Box
Black Box involves testing
system/components considering inputs,
outputs and general functionalities as defined
in requirement specifications.
It does not consider any internal processing
by the system.
Black box testing is independent of platform,
database, and system to make sure that the
system works as per requirement defined as
well as implied ones.
Software Testing
By Milind G. Limaye
91
W|I|N|D|U
Advantage
Blackbox testing is the only method to prove
that software does what it is supposed to do
and it does not do something which can
cause a problem to user/customer
It is the only method to show that software is
living and it really works
Some types of testing can be done only by
black box testing methodologies, for
example, performance and security
Software Testing
By Milind G. Limaye
92
W|I|N|D|U
Disadvantage
Some logical errors in coding can be
missed in black box testing.
Some redudant testing is possible as
requirements may execute the same
branch of code again and again.
Software Testing
By Milind G. Limaye
93
W|I|N|D|U
Black Box
TestCase Designing Methodologies
Black Box testing methodology defines how
the user is going to interact with the system
without any assumption about how the
system is built.
94
W|I|N|D|U
White Box
Input
WHITE BOX
Output
Events,
Standards
Software Testing
By Milind G. Limaye
95
W|I|N|D|U
96
W|I|N|D|U
97
W|I|N|D|U
Gray Box
Input
GRAY BOX
Output
Events,
Standards
Software Testing
By Milind G. Limaye
98
W|I|N|D|U
W|I|N|D|U
Advantages
Gray box testing tries to combine the
advantages of white box testing and black box
testing. It check whether the work product
works in a correct manner, both functionally as
well as structurally
Disadvantages
Generally, gray box testing is conducted with
some automation tools. Knowledge of such
tools along with their configuration is essential
for performing gray box testing.
100
W|I|N|D|U
Web Project
Management
W|I|N|D|U
W|I|N|D|U
From
W|I|N|D|U
From
W|I|N|D|U
W|I|N|D|U
Specifics
W|I|N|D|U
W|I|N|D|U
Challenges
in Web Project
Management
Leadership challengers
Retschitzegger
W|I|N|D|U
Development
Challenges
W|I|N|D|U
Monitoring
W|I|N|D|U
Development-related
Challenges in
Web Projects
Novelty
Dynamics
Parallelism
Continuity
Juvenile
Immaturity
W|I|N|D|U
W|I|N|D|U
W|I|N|D|U
The
W|I|N|D|U
W|I|N|D|U
Risk
Management
W|I|N|D|U
ISO 9126
117