Needing computer science homework completed
W1 Assignment #1 & W1 Assignment #2
_____________________________________
Examples and Readings:
Document W1 A1 Example is for (Assignment #1)
All other documents is for (Assignment #2)
Need (1) Paragraph for each
DQ
This week contains multiple discussion questions that you are required to answer.
DQ#1 – Introduction/ Experience with Analysis and Design
Please start the discussion by introducing yourself. Have you ever worked with any systems analysis and design task? Have you ever seen a PRD (Product Requirement Document) or a TDD (Technical Design Document)? What is your expectation for this class?
DQ#2 – Requirement Gathering
If you do not have a strong business process background, or very much knowledge about the problem domain (e.g. the business area being supported), how do you ensure that you have gathered all the important requirements and that your requirements are accurate, thorough, and comprehensive?
DQ#3 – Use Case Identification Techniques
The book discusses two techniques for identifying use cases (the event decomposition technique and the user goal technique). Which technique is better? Why?
DQ#4 – Problem Domain Class Identification
The book discusses two techniques to identify classes from the problem domain (The Brainstorming technique and the Noun technique). Which technique is better? When might one be better than the other? When might it be appropriate to use both techniques?
|
Hide Assignment Information |
|
|
Instructions |
|
|
Individual Assignments: ParkingFinder.com is a type of e-business exchange that does business entirely on the Internet. The system connects parking space landlords and space tenants all over the world in an online market and manages the entire booking process and payments. For a person to offer parking spaces (landlord), he/she must register with ParkingFinder.com. The person must provide a current physical address and telephone number as well as a current e-mail address. The system will then maintain an open account for this person. Access to the system as a landlord is through a secure, authenticated portal. A landlord can list parking spaces on the system through a special Internet form. Information required includes all of the pertinent information about the parking space, the asking price, and documents showing that the landlord has the right to rent the space. A landlord may list as many spaces as desired. Parking spaces listed by a landlord need to be verified that the landlord owns them, before they can be visible to the public. The system maintains an index of all parking spaces in the system so that tenants can use the search engine to search for parking spaces. The search engine allows searches of parking spaces by location. At the end of each month, a check is mailed to each landlord for the spaces that have been rented. People wanting to rent parking spaces (potential tenants) come to the site and search for the space they want. When they decide to book, they must open an account with a credit card to pay for the parking space. They need to select the space they want to book, the time slot for the renting period and the vehicle license plate number. The system maintains all of this information on secure servers. The tenants can, if they want, enter their review and ratings of the parking space. The same functionality can be accessed through mobile app, which can be downloaded and installed from Apple Store and Google Play Store. Week 1: · 1. Identify (at least 5) use cases for the system using the user goal technique. List User User Goal Use Case Name Brief Description
2. Use a UML Editor (for example MS Visio with UML template) to draw a 3. List 5 non-functional requirements of the system – Usability, Reliability, Performance, Security and Design Constraints (5 points) |
FirstName LastName
CIS320 Week 1 Assignment
Professor Tuan Do, Ph.D., PMP
National University
08Aug2018
1. Identify (at least 5) use cases for the system using the user goal technique. List the users,
user goals, resulting use cases and write a brief use case description for each resulting
use case. (10 points)
Actors: Buyer, Seller, Employees
Users User Goal Use Case Brief Description
Buyer Register individual
information on the
website to buy books
Register on the website Opening an account on the
system
Seller Register individual
information on the
website to sell books
Register on the website Opening an account on the
system
Buyer Search for books by
to buy/purchase
Search for book Books can be searched by
Title, Author, Category or
Key Word
Buyer Request from seller
to purchase the book
or books chosen
Request to Purchase
Book
1. EyesHaveIt sends
email notice to Seller
of book chosen
2. Book marked as
purchased
3. Maintains invoice
until book shipped by
seller
Seller Ship the book to the
buyer
Ship Book 1. Seller accepts
purchase
2. Seller notifies Buyer
via email within 48
hours that purchase is
noted.
3. Seller sends book to
Buyer and sends
notification to both
Buyer and EyesHaveIt
that shipment is made
Employees Change/Update
information on book
purchased in the
EyesHaveIt website
Adjust Purchase
Information
1. Email from Seller
received that shipment
was made.
2. EyesHaveIt Changes
order to “Shipped”
Status.
3. Date annotated for 30
This study source was downloaded by 100000783814751 from CourseHero.com on 03-03-2023 09:58:47 GMT -06:00
https://www.coursehero.com/file/36834406/CH-CIS320-WK1docx/
https://www.coursehero.com/file/36834406/CH-CIS320-WK1docx/
day wait period and
Service Code
Response.
Buyer Enters a rating code
to determine
condition of the book
received and Seller
Service
Enter Service Code 1. This is a rating system
for the seller and
customer satisfaction
indicator.
2. Buyer submits rating
for condition of the
book and how well the
Seller is servicing the
books.
Seller Register information
about the Book the
seller wishes to sell
Register the Book 1. Book form is
submitted for Title,
Author, Category,
General Condition and
asking price.
2. More than one book
can be listed by a
seller.
Employees Send the money
received for the
purchased book from
the Buyer to the
Seller
Send Money to Sellers At the end of every
month all sold books
that have completed
the 30 days wait
period and the Service
Code has been entered
by Buyer the money is
sent to the Seller.
This study source was downloaded by 100000783814751 from CourseHero.com on 03-03-2023 09:58:47 GMT -06:00
https://www.coursehero.com/file/36834406/CH-CIS320-WK1docx/
https://www.coursehero.com/file/36834406/CH-CIS320-WK1docx/
2. Use a UML Editor (for example MS Visio with UML template) to draw a use case
diagram based on the actors and use cases you identified (10 points)
This study source was downloaded by 100000783814751 from CourseHero.com on 03-03-2023 09:58:47 GMT -06:00
https://www.coursehero.com/file/36834406/CH-CIS320-WK1docx/
Powered by TCPDF (www.tcpdf.org)
https://www.coursehero.com/file/36834406/CH-CIS320-WK1docx/
http://www.tcpdf.org
CIS320
Systems Analysis and Integration
Week 1 – Use Cases
*
Systems Analysis and Design in a Changing World, 6th Edition
*
Chapter 3
Overview
This chapter focuses on identifying and modeling the key aspect of functional requirements– use cases
Outline
Use Cases and User Goals
Use Cases and Event Decomposition
Use Cases and CRUD
User Case Diagrams
Systems Analysis and Design in a Changing World, 6th Edition
*
Systems Analysis and Design in a Changing World, 6th Edition
*
Use Cases
Use case— an activity that the system performs, usually in response to a request by a user
Use cases define functional requirements
Analysts decompose the system into a set of use cases (functional decomposition)
Two techniques for Identifying use cases
User goal technique
Event decomposition technique
CRUD technique is used for validating, cross-checking
Name each use case using Verb-Noun
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
User Goal Technique
This technique is the most common in industry
Simple and effective
Identify all of the potential categories of users of the system
Interview and ask them to describe the tasks the computer can help them with
Probe further to refine the tasks into specific user goals, “I need to Ship items, Track a shipment, Create a return”
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
User Goal Technique
Some RMO CSMS Users and Goals
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
User Goal Technique:
Specific Steps
Identify all the potential users for the new system
Classify the potential users in terms of their functional role (e.g., shipping, marketing, sales)
Further classify potential users by organizational level (e.g., operational, management, executive)
For each type of user, interview them to find a list of specific goals they will have when using the new system (current goals and innovative functions to add value)
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
User Goal Technique
Specific Steps (continued)
Create a list of preliminary use cases organized by type of user
Look for duplicates with similar use case names and resolve inconsistencies
Identify where different types of users need the same use cases
Review the completed list with each type of user and then with interested stakeholders
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Event Decomposition Technique
More Comprehensive and Complete Technique
Identify the events that occur to which the system must respond.
For each event, name a use case (verb-noun) that describes what the system does when the event occurs
Event– something that occurs at a specific time and place, can be described, and should be remembered by the system
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Events and Use Cases
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Types of Events
External Event
an event that occurs outside the system, usually initiated by an external agent or actor
Example: Customer places an order
Temporal Event
an event that occurs as a result of reaching a point in time
Example: It’s month’s end and the expense report needs to be printed
State Event
an event that occurs when something happens inside the system that triggers some process
Example: reorder point is reached for inventory item
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Event Decomposition Technique:
Specific Steps
Consider the external events in the system environment that require a response from the system by using the checklist shown in Figure 3-3
For each external event, identify and name the use case that the system requires
Consider the temporal events that require a response from the system by using the checklist shown in Figure 3-4
For each temporal event, identify and name the use case that the system requires and then establish the point of time that will trigger the use case
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Event Decomposition Technique:
Specific Steps (continued)
Consider the state events that the system might respond to, particularly if it is a real-time system in which devices or internal state changes trigger use cases.
For each state event, identify and name the use case that the system requires and then define the state change.
When events and use cases are defined, check to see if they are required by using the perfect technology assumption. Do not include events that involve such system controls as login, logout, change password, and backup or restore the database, as these are put in later.
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Event Decomposition Technique: Benefits
Events are broader than user goal: Capture temporal and state events
Help decompose at the right level of analysis: an elementary business process (EBP)
EBP is a fundamental business process performed by one person, in one place, in response to a business event
Uses perfect technology assumption to make sure functions that support the users work are identified and not additional functions for security and system controls
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Use Cases and CRUD Technique
CRUD is Create, Read/Report, Update, and Delete (archive)
Often introduced in database context
Technique to validate, refine or cross-check use cases
NOT for primarily identifying use cases
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Use Case Diagrams
Use case diagram— a UML model used to graphically show uses cases and their relationships to actors
Actor is the UML name for a end user
Automation boundary— the boundary between the computerized portion of the application and the users who operate the application
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Use Case Diagram – Example
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Use Case Diagrams
The <
A relationship between use cases where one use case is stereotypically included within the other use case— like a called subroutine. Arrow points to subroutine
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Use Case Diagrams:
Steps
Identify all the stakeholders and users who would benefit by seeing a use case diagram
Determine what each stakeholder or user needs to review in a use case diagram: each subsystem, for each type of user, for use cases that are of interest
For each potential communication need, select the use cases and actors to show and draw the use case diagram. There are many software packages that can be used to draw use case diagrams
Carefully name each use case diagram and then note how and when the diagram should be used to review use cases with stakeholders and users
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Summary
Use cases are the functions identified, the activities the system carries out usually in response to a user request
Two techniques for identifying use cases are the user goal technique and the event decomposition technique
The user goal technique begins by identifying end users called actors and asking what specific goals they have when interacting with the system
The event decomposition technique begins by identifying events that occur that require the system to respond.
The CRUD technique is used to validate and refine the use cases identified
Systems Analysis and Design in a Changing World, 6th Edition
CIS320
Systems Analysis and Integration
Week 1 – Domain Modeling
*
Systems Analysis and Design in a Changing World, 6th Edition
*
Chapter 4 Outline
Overview
This chapter focuses on another key concepts for defining requirements— data entities or domain classes (what need to be remembered!)
Outline
“Things” in the Problem Domain
Data entities
Domain classes
The Domain Model Class Diagram
Systems Analysis and Design in a Changing World, 6th Edition
*
Systems Analysis and Design in a Changing World, 6th Edition
*
Things in the Problem Domain
Problem domain—the specific area (or domain) of the users’ business need that is within the scope of the new system.
“Things” are those items users work with when accomplishing tasks that need to be remembered
Examples of “Things” are products, sales, shippers, customers, invoices, payments, etc.
These “Things” are modeled as domain classes or data entities
In this course, we will call them domain classes. In database class you call them data entities
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Things in the Problem Domain
Two Techniques for Identifying them
Brainstorming Technique
Use a checklist of all of the usual types of things typically found and brainstorm to identify domain classes of each type
Noun Technique
Identify all of the nouns that come up when the system is described and determine if each is a domain class, an attribute, or not something we need to remember
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Brainstorming Technique
Are there any tangible things? Are there any organizational units? Sites/locations? Are there incidents or events that need to be recorded?
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
The Noun Technique
A technique to identify problem domain classes (things) by finding, classifying, and refining a list of nouns that come up in in discussions or documents
Popular technique. Systematic.
Does end up with long lists and many nouns that are not things that need to be stored by the system
Difficulty identifying synonyms and things that are really attributes
Good place to start when there are no users available to help brainstorm
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Partial List of Nouns for RMO
With notes on whether to include as domain class
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Details about Domain Classes
Attribute— describes one piece of information about each instance of the class
Customer has first name, last name, phone number
Identifier or key
One attribute uniquely identifies an instance of the class. Required for data entities, optional for domain classes. Customer ID identifies a customer
Compound attribute
Two or more attributes combined into one structure to simplify the model. (E.g., address rather than including number, street, city, state, zip separately). Sometimes an identifier or key is a compound attribute.
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Attributes and Values
Class is a type of thing.
Object is a specific instance of the class. Each instance has its own values for an attribute
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Associations Among Things
Association— a naturally occurring relationship between classes (UML term)
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Minimum and Maximum Multiplicity
Associations have minimum and maximum constraints
minimum is zero, the association is optional
If minimum is at least one, the association is mandatory
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Types of Associations
Binary Association
Associations between exactly two different classes
Course Section includes Students
Members join Club
Unary Association (recursive)
Associations between two instances of the same class
Person married to person
Part is made using parts
Ternary Association (three)
N-ary Association (between n)
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Semantic Net
Shows instances and how they are linked
Example shows instances of three classes
Quick quiz:
How many associations are there?
What are the minimum and maximum multiplicities in each direction?
What type of associations are they?
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
The Domain Model Class Diagram
Class
A category of classification used to describe a collection of objects
Domain Class
Classes that describe objects in the problem domain
Class Diagram
A UML diagram that shows classes with attributes and associations (plus methods if it models software classes)
Domain Model Class Diagram
A class diagram that only includes classes from the problem domain, not software classes so no methods
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Domain Class Notation
Domain class has no methods
Class name is always capitalized
Attribute names are not capitalized and use camelback notation (words run together and second word is capitalized)
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
A Simple Domain Model Class Diagram
Note: This diagram matches the semantic net shown previously
A customer places zero or more orders
An order is placed by exactly one customer
An order consists of one or more order items
An order item is part of exactly one order
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
UML Notation for Multiplicity
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
More Complex Issues about Classes:
Generalization/Specialization Relationships
Generalization/Specialization
A hierarchical relationship where subordinate classes are special types of the superior classes. Often called an Inheritance Hierarchy
Superclass
the superior or more general class in a generalization/specialization hierarchy
Subclass
the subordinate or more specialized class in a generalization/specialization hierarchy
Inheritance
the concept that subclasses classes inherit characteristics of the more general superclass
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Generalization/Specialization
Inheritance for RMO Three Types of Sales
Abstract class— a class that allow subclasses to inherit characteristics but never gets instantiated. In Italics (Sale above)
Concrete class— a class that can have instances
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
More Complex Issues about Classes:
Whole Part Relationships
Whole-part relationship— a relationship between classes where one class is part of or a component portion of another class
Aggregation— a whole part relationship where the component part exists separately and can be removed and replaced (UML diamond symbol, next slide)
Computer has disk storage devices
Car has wheels
Composition— a whole part relationship where the parts can no longer be removed (filled in diamond symbol)
Hand has fingers
Chip has circuits
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Whole Part Relationships
Computer and its Parts
Note: this is composition, with diamond symbol.
Whole part can have multiplicity symbols, too (not shown)
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
More on UML Relationships
There are actually three types of relationships in class diagrams
Association Relationships
These are associations discussed previously, just like ERD relationships
Whole Part Relationships
One class is a component or part of another class
Generalizations/Specialization Relationships
Inheritance
So, try not to confuse relationship with association
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Summary
This chapter focuses on modeling functional requirements of “things or items” that need to be remembered!
“Things” in the problem domain are identified and modeled, called domain classes or data entities
Two techniques for identifying domain classes/data entities are the brainstorming technique and the noun technique
Domain classes have attributes and associations
Associations are naturally occurring relationships among classes, and associations have minimum and maximum multiplicity
There are actually three UML class diagram relationships: association relationships, generalization/specialization (inheritance) relationships, and whole part relationships
Systems Analysis and Design in a Changing World, 6th Edition
CIS320
Systems Analysis and Integration
Week 1 – System Development Life Cycle
*
Systems Analysis and Design in a Changing World, 6th Edition
*
SDLC – System Development Life Cycle
SDLC – the entire process consisting of all activities required to build, launch, and maintain an information system
Identify the problem or need and obtain approval
Plan and monitor the project
Discover and understand the details of the problem or need
Design the system components that solve the problem or satisfy the need
Build, test, and integrate system components
Complete system tests and then deploy the solution
Agile SDLC: responsive to change
Iterative SDLC: development through multiple iterations
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Iterative and Agile Systems Development Lifecycle (SDLC)
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Activities of Core Process 1:
Identify Problem and Obtain Approval
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Activities of Core Process 2:
Plan and Monitor the Project
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Systems Analysis Activities
Involve discovery and understanding
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Design Activities
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Implementation and Deployment Activities
Systems Analysis and Design in a Changing World, 6th Edition
CIS320
Systems Analysis and Integration
Week 1
System Requirements
Information Gathering Technique
*
Systems Analysis and Design in a Changing World, 6th Edition
*
Chapter 2
Overview
This chapter focuses on Core Process 3 (Systems analysis activities, tools and techniques) to discover and understand the details of the problem or need
Outline
Systems Analysis Activities
What Are Requirements?
Models and Modeling
Stakeholders
Information-Gathering Techniques
Documenting Workflows with Activity Diagrams
Systems Analysis and Design in a Changing World, 6th Edition
*
Systems Analysis and Design in a Changing World, 6th Edition
*
Systems Analysis Activities
Involve discovery and understanding
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Systems Analysis Activities
Gather Detailed Information
Interviews, questionnaires, documents, observing business processes, researching vendors, comments and suggestions
Define Requirements
Modeling functional requirements and non-functional requirements
Prioritize Requirements
Essential, important, vs. nice to have
Develop User-Interface Dialogs
Flow of interaction between user and system
Evaluate Requirements with Users
User involvement, feedback, adapt to changes
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
What Are Requirements?
System Requirements =
Functional requirements
Non-functional requirements
Functional Requirements– the activities the system must perform
Business uses, functions the users carry out
Non-Functional Requirements– other system characteristics
Constraints and performance goals
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
FURPS+ Requirements Acronym
Systems Analysis and Design in a Changing World, 6th Edition
Which requirements are these?
Reliability
Design Constraints
Performance
Functional
Security
Usability
The user must be able to add items to the shopping cart, check out and place order.
User should need no more than 5 clicks to complete an order.
Average response time should be less than 300 ms. Maximal response time is no longer than 2 seconds.
The website requires Javascript to be turned on.
The website should achieve at least 99.99 uptime.
Users must use HTTPS for checkout
_______ requirements describe…
Design Constraint
Functional
Performance
Security
Reliability
Usability
the activities that the system must perform
operational characteristics related to users, such as the user interface, related work procedures, on-line help and documentation
operational characteristics related to measures of workload, such as throughput and response time
operational characteristics related to the environment, hardware, and software
the dependability of a system, that is, how often it exhibits behaviors such as service outages and incorrect processing
which users can perform what system functions under what conditions
Systems Analysis and Design in a Changing World, 6th Edition
*
Models and Modeling
How do we define requirements?
After collecting information, create models
Model– a representation of some aspect of the system being built
Types of Models
Textual model– something written down, described
Graphical models– diagram, schematic
Mathematical models– formulas, statistics, algorithms
Unified Modeling Language (UML)
Standard graphical modeling symbols/terminology used for information systems
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Information Gathering Techniques
Interviewing users and other stakeholders
Distributing and collecting questionnaires
Reviewing inputs, outputs, and documentation
Observing and documenting business procedures
Researching vendor solutions
Collecting active user comments and suggestions
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
1. Interviewing Users and Other Stakeholders
Prepare detailed questions
Meet with individuals or groups of users
Obtain and discuss answers to the questions
Document the answers
Follow up as needed in future meetings or interviews
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
2. Distribute and Collect Questionnaires
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
3. Review Inputs, Outputs, and Procedures
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Additional Techniques
4. Observe and Document Business Processes
Watch and learn
Document with Activity diagram (next section)
5. Research Vendor Solutions
See what others have done for similar situations
White papers, vendor literature, competitors
6. Collect Active User Comments and Suggestions
Feedback on models and tests
Users know it when the see it
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Documenting Workflows/Business Processes with Activity Diagrams
Workflow– sequence of processing steps that completely handles one business transaction or customer request
Activity Diagram– describes user (or system) activities, the person who does each activity, and the sequential flow of these activities
Useful for showing a graphical model of a workflow
A UML diagram
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Activity Diagrams Symbols
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Activity Diagram for RMO Order Fulfillment
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Summary
Systems analysis activates correspond to the core SDLC process Discover and understand details
Systems analysis involves defining system requirements– functional and non-functional
Analysis activities include
Gather detailed information
Define requirements
Prioritize requirements
Develop user-interface dialogs
Evaluate requirements with users
FURPS+ is the acronym for functional, usability, reliability, performance, and security requirements
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Summary
Models and modeling are used to explore and document requirements
A model represents some aspect of a system, and can include textual, graphical, and mathematical models
Unified Modeling Language (UML) is the standard set of notations and terminology for information systems models
Information gathering techniques are used to collect information about the project
Interviews, questionnaires, reviewing documents, observing business processes, researching vendors, comments and suggestions
The UML Activity Diagram is used to document (model) workflows/business processes after collecting information
Systems Analysis and Design in a Changing World, 6th Edition
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
