Bachelor's degree computer science (21) Programming Exercises Part 3

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
System Sequence Diagrams
Clarke, R. J (2001) S213-02: 1 Multimedia in Organisations BUSS 213 Supplementary 2 Use Cases & Descriptions.
NJIT 1 Domain Model Visualizing Concepts Chapter 9 Applying UML and Patterns Craig Larman.
UML Activity Diagram. Activity Diagram  The main reason to use activity diagrams is to model the workflow behind the system being designed.  Activity.
1 SYSTEMS DESIGN Pertemuan 13 s.d 20 Matakuliah: A0554/Analisa dan Perancangan Sistem Informasi Akuntansi Tahun: 2006.
COMP 350: Object Oriented Analysis and Design Lecture 2
Chapter 13: Designing the User Interface
The Computer Science Course at Omar Al-Mukhtar University, Libya The Computer Science Course at Omar Al-Mukhtar University, Libya User-Centered Design.
Ideas on Information Architecture Defining the Job –Goals What is the Mission/purpose of the website? What do you want to accomplish with the website?
Object Oriented Analysis By: Don Villanueva CS 524 Software Engineering I Fall I 2007 – Sheldon X. Liang, Ph. D.
Use Case. 2 Copyright e-Government Program (Yesser) Use Case - Summary Slide  Use Cases – Definition  The purpose of use cases  Why use use cases?
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
1 Project Name Team Lead Location Month XX, Year.
LECTURE 3 USE CASE DESCRIPTION. Use Cases grouped into system modules Note: Same actor interacts with different modules USE CASE DIAGRAM OF THE CUSTOMER.
Internet Software Development Putting it all together Paul J Krause.
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
SacProNet An Overview of Project Management Techniques.
Chapter 7 Applying UML and Patterns Craig Larman
Bachelor of Information Technology 1. SepaliProject\Sound\Start.wav 2. University of Colombo School of Computing No. 35, Reid Avenue. Colombo 07 SepaliProject\Sound\Start.wav.
Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University.
Use Case Modeling Chapter 7 Part of Requirements Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
 Relate Use Cases to  MVC and Application Architecture  CRC  Recap distinctions : Language, Process, Tool  Detail a Use Case  Elements of a Use Case.
Lecture 4 :Use cases III (UC description) 1. Outline CT 1414 * Nouf Aljaffan2  Concept of Use Case Description  Levels of Use Case Description  Reading.
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
The College Of Applied Studies And Community Services Lecture 3 :Use cases II (UC description) Systems Analysis & Design Instructor: Nouf Aljaffan CT 1414.
Scenario A scenario is a sequence of steps describing an interaction between a user and a system. Use case is a set of scenarios tied together by a common.
A Well Designed Web Application The Benefits of Object Oriented Analysis and Design Simone Becker
Spring 2007 Week 10: Object Modeling (1)Use Case Model IFS410: Advanced Analysis and Design.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
1 CEN 4020 Software Engineering PPT4: Requirement analysis.
1 Annotation Framework March Terminology CV - abbreviation for controlled vocabulary CRS - Community Review System (a collection within DLESE)
George Wang, Ph.D. COMP 380/L Lesson 2. Use Case Use cases are a way to capture system functionalities (i.e., functional requirements) Based on use case.
Requirements Models Representing the Product in Ways Other than Text.
Project management processes of a project
Pepper modifying Sommerville's Book slides
Use Case Analysis Chapter 6.
Investigating System Requirements
CompSci 280 S Introduction to Software Development
Welcome to M301 P2 Software Systems & their Development
Software Engineering Lecture 4 System Modeling The Analysis Stage.
CMPE 280 Web UI Design and Development August 29 Class Meeting
Chapter 4 – Requirements Engineering
Z556 Systems Analysis & Design
Sample Text for Title of Poster
CGS 2545: Database Concepts Fall 2010
BTS430 Systems Analysis and Design using UML
CHU HAI COLLEGE OF HIGHER EDUCATION DEPARTMENT OF COMPUTER SCIENCE Preparation of Mid-Term Progress Report Bachelor of Science in Computer Science.
Week 10: Object Modeling (1)Use Case Model
EKT 421 SOFTWARE ENGINEERING
System Modeling Chapter 4
Use Case Model Use case description.
Object-Orientated Analysis, Design and Programming
COMP 350: Object Oriented Analysis and Design Lecture 2
Chapter 3: The Requirements Workflow
Summarizing Our Models to Date
Concepts, Specifications, and Diagrams
Object Oriented Analysis and Design
Examples and general guides
INFS 6225 Object Oriented Systems Analysis & Design
More Requirements Models
Domain Modeling.
Object-Oriented Software Engineering
Use Case Modeling Part of the unified modeling language (U M L)
Sample Text for Title of Poster
Sample Text for Title of Poster
Scrum in Action.
Presentation transcript:

Bachelor's degree computer science (21) Programming Exercises Part 3 The object-oriented analysis (OOA) proposed steps:

Systemidee and objective What is to be achieved, ideas, visions, intentions and desires. Free text, approximately half of the page.

Anforderungsbeitragende (stakeholders) Identify Customer Legislators Projektbetroffene Systembetroffene User Customers Support Sales  Wished Tabular distinction in:  Subject Matter Experts, Anforderungsverantwortliche And Systembetroffene/actors.

Identify business processes Systemidee with UML Use Case Diagram Use Case Diagram, "workflow") visualize.  Business processes with a UML-activity diagram (flow chart with a consecutive steps) abstract describe.  Technical and abstract describe the business stakeholders. A Use Case (Use Case) Describes a time-continuous interaction with a system one or more players. A Business Process There may be made up of several use cases and provides a summary of professional activities that are carried out related to a business transaction to edit results-oriented. A Business Transaction (E.g. application) is caused by an event (e.g. date of receipt) and has technical results (e.g. contract).

Interests of the Anforderungsbeitragenden (stakeholders) identify: Description of the objectives and interests, as a bulleted list of important system properties and identification of problems and weaknesses, everything from the point of view of the Anforderungsbeitragenden.

Geschaftsanwendungsfalle (business use case) Identify Identification of the Geschaftsanwendungsfalle ( "business") (possibly in the form of Stories) And Their triggers and results as well as identify excludable Geschaftsanwendungsfalle ( "business" {excluded} ). A Geschaftsanwendungsfall (the business case, Business Use Case) Describes a use case in an abstract technical form from the point of view of the user.

...