What is the difference between user-interface design and system-interface design? Which diagrams developed in the analysis can be used for the user-interface design an
Needing computer science homework completed
W2 Assignment #1 & W2 Assignment #2
_____________________________________
Examples and Readings:
Document CH_CIS320_WK2.1 EXAMPLE.docx is for (Assignment #1)
All other documents is for (Assignment #1 & Assignment #2)
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 2:
4. Based on the information here, draw a domain model class diagram (UML Class Diagram) for the system that includes classes, attributes, association relationships, cardinality (10 points)
5. For each of the two use cases List a Parking Space and Book a Parking Space, develop a fully developed use case description and a System Sequence Diagram (SSD) (20 points)
,
Need 2 Paragraph’s for each DQ
DQ#1 – Systems Analysis vs. Systems Design
What is the difference between systems analysis and systems design?
DQ#2 – User-interface Design vs. System-interface Design
What is the difference between user-interface design and system-interface design? Which diagrams developed in the analysis can be used for the user-interface design and system-interface design? How?
Start a New Thread
DQ#3 – Architectural Design vs. Detail Design
What is the difference between architectural design and detail design?
DQ#4 – NU Website and BrightSpace Improvement Suggestion
The National University (NU) website and the BrightSpace software provide the online teaching and learning environment for both faculties and students. We all sometimes feel that both the NU website and the BrightSpace software can be improved to facilitate the teaching and learning process of faculties and students.
Please suggest some improvements for the NU website and BrightSpace software. Describe your improvement requirements using the concepts that we have learned in the first week (FURPS+ Model, Use Cases, SSD for Input/Output, Activity Diagrams for Workflow etc.).
,
First Last CIS320 Week 2 Assignment Professor Tuan Do, Ph.D., PMP National University 15Aug2018
1. Based on the information here, draw a domain model class diagram (UML Class Diagram) for the system that includes classes, attributes, association relationships, cardinality. Make sure that you identify at least one generalization/specialization relationship and include it in your domain model class diagram. (10 points)
EyesHaveit.com
This study source was downloaded by 100000783814751 from CourseHero.com on 03-06-2023 18:35:57 GMT -06:00
https://www.coursehero.com/file/36834401/CH-CIS320-WK21docx/
2. For each of the two use cases Register as Seller and Purchase Books, develop a fully developed use case description and a System Sequence Diagram (SSD). (20 points)
Use Case Name: Register as Seller Scenario: Person decides to register as a Seller to sell books Triggering Event: Person decides that they would like to sell books Brief Description: The person would register on the website with name, address, email
and phone number. When deciding to sell, then the person would register as a seller and fill out a form for the book they want to sell. The form lists the book’s author, title, category, description and general condition.
Actors: Seller Stakeholders: Seller, Buyers and EyesHaveIt Company Preconditions: Person registered on EyesHaveIt and Person has book to sell Postconditions: Seller is registered with at least one book listed. Flow of Activities Actor: System:
1. Person registers on website
1.1 System stores Name, Address, Phone Number and Email address
2. Person registers as Seller
2.1 System assigns SellerID 2.2 System creates Seller account 2.3 System changes screen to
Special Internet Form for book(s)
3. Seller fills out book information on form
3.1 System creates BookID 3.2 System creates book record and
stores book information ` 4. Repeat step 3 if
more than one book or close out Special Internet Form
4.1 Repeat 3.x
5. Seller is registered logs off website
5.1 Website closes connection
Exception Conditions: Person not registered on EyesHaveIt System or there is no book to sell.
This study source was downloaded by 100000783814751 from CourseHero.com on 03-06-2023 18:35:57 GMT -06:00
https://www.coursehero.com/file/36834401/CH-CIS320-WK21docx/
SSD for Register as Seller:
This study source was downloaded by 100000783814751 from CourseHero.com on 03-06-2023 18:35:57 GMT -06:00
https://www.coursehero.com/file/36834401/CH-CIS320-WK21docx/
Use Case Name: Purchase Books Scenario: Buyer finds a book and then purchases it. Triggering Event: Buyer decides to buy a book from EyesHaveIt. Brief Description: Person searches the system database for a book and then selects it for
purchase. There maybe more than one book. After selection EyesHaveit change information of books to “sold” and then sends email to Seller for confirmation with a 48H deadline. Seller confirms purchase and notifies EyesHaveit when shipment of book has been made. Buyer receives book and select a ServiceCode for satisfaction and to confirm book received in condition advertised. EyesHaveIt records information and at the end of the month sends money to Seller after 30 days post book shipment with confirmation that book has been sent and satisfaction code has been recorded.
Actors: Buyer, Stakeholders: Buyer, Seller, EyesHaveIt company Preconditions: Book details must be present in the system, Seller and Buyer must be
registered prior to purchase. Postconditions: Book information must be updated after purchase.
Email must be sent to seller. Buyer must enter service code for seller to be paid.
Flow of Activities Actor: System: 1. Person Registers on
EyesHaveIt System 1.1 System creates PersonID 1.2 System creates record with
Name, Address, Phone Number and Email.
2. Person searches the website of EyesHaveIt.com to find a book
2.1 Match all books from search and lists.
3. Person selects a book from the book list and puts into cart.
3.1 Create shopping cart associated with PersonID
3.2 Put BookID into shopping cart
4. Repeat step 2 & 3 until Person is finished
4.1 Repeat step 2.X and 3.X
5. Person selects Checkout.
5.1 System prompts for Buyer Login
6. Person logins in with Buyer Login or Registers at this time as a Buyer
6.1 System returns Buyers record or prompts for registration as Buyer
6.2 If registering as Buyer a Buyer ID is created and information is
This study source was downloaded by 100000783814751 from CourseHero.com on 03-06-2023 18:35:57 GMT -06:00
https://www.coursehero.com/file/36834401/CH-CIS320-WK21docx/
stored as a Buyer Record 7. Buyer selects
Checkout 7.1 System changes book(s) status
to sold 7.2 System charges credit card
information 7.3 System sends email to Seller.
Exception Conditions: Person is not registered as a Buyer. Book is not listed.
SSD for Purchase Books:
This study source was downloaded by 100000783814751 from CourseHero.com on 03-06-2023 18:35:57 GMT -06:00
https://www.coursehero.com/file/36834401/CH-CIS320-WK21docx/ Powered by TCPDF (www.tcpdf.org)
,[removed],
CIS320
Systems Analysis and Integration
Week 2 – User and System Interface Design
*
Systems Analysis and Design in a Changing World, 6th Edition
*
Chapter 7 Outline
- User and System Interfaces
- Understanding the User Interface
- User-Interface Design Concepts
- The Transition from Analysis to User-Interface Design
- User-Interface Design
- Identifying System Interfaces
- Designing System Inputs
- Designing System Outputs
Systems Analysis and Design in a Changing World, 6th Edition
*
Systems Analysis and Design in a Changing World, 6th Edition
*
Overview
- Information systems interact with people and other systems
- Poorly designed user interface can make the information system unusable
- Poorly designed system interfaces are a source of errors and inefficiency
- User and system interfaces involve both inputs and outputs and involve a large number of stakeholders
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
User Interfaces
and System Interfaces
- User Interface – inputs and outputs that directly involve a human user/actor
- A dialog goes on between actor and system
- System Interface – the inputs and outputs that require minimal human intervention (mostly about communication between system and system)
- Inputs captured automatically
- Outputs direct to other systems
- Printed and distributed outputs (statements, reports)
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
User Centered Design
- Design techniques that embody the view that the user interface is the system to the user
- Dates back to the 1980s (more for Mac)
- Principles of User Centered Design
- Focus early on users and their work
- Evaluate designs to ensure usability
- Use iterative development
- Note that contemporary A&D finally incorporates these principles
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Three Components of the User Interface
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Metaphors of Human Computer Interaction
- Direct manipulation metaphor
- metaphor in which objects on a display are manipulated to look like physical objects (pictures) or graphic symbols that represent them (icons)
- Desktop metaphor
- metaphor in which the visual display is organized into distinct regions, with a large empty workspace in the middle and a collection of tool icons around the perimeter
- Document metaphor
- metaphor in which data is visually represented as paper pages or forms
- Dialog metaphor
- metaphor in which user and computer accomplish a task by engaging in a conversation or dialog via text, voice, or tools such as labeled buttons
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Metaphor Details
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Direct Manipulation, Desktop, and Document Metaphors On One Screen
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Dialog Metaphor
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Use Cases and the Menu Hierarchy
- We design use case by use case
- Menus are a typical way to organize access to use case functionality
- Different types of users might have different menus
- Useful to design an overall menu hierarchy and then subsets for different users
- Once the hierarchy is established, menus can be implemented in a variety of ways
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Dialog Design
- For each use case, think of the natural flow of a dialog between user and computer
- Based on the flow of activities in use case description and/or the system sequence diagram
- Use natural language to emphasize feedback to user
- Create a storyboard of the dialog, showing the sequence of sketches of the screen each step of the dialog. (storyboarding)
- Review the storyboard with users
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
From Dialog to Storyboard (part 1)
Use case Check out shopping cart
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
From Dialog to Storyboard (part 1)
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
From Dialog to Storyboard (part 2)
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
From Dialog to Storyboard (part 2)
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Identifying System Interfaces
Inputs/outputs with minimal human intervention
- Inputs from and outputs to other systems
- These are direct interfaces with other information systems, normally formatted as network messages.
- Highly automated inputs and outputs
- These are captured by devices (such as scanners) or generated by persons who start a process that proceeds without further human intervention.
- Inputs and outputs to external databases
- These can supply input to or accept output from a system.
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Identifying System Interfaces
Systems Analysis and Design in a Changing World, 6th Edition
*
XML for System Interfaces
- Extensible Markup Language (XML) — embeds self-defining data structures within textual messages
- XML tags — character sequences (such as <name> and </name>) that define the beginning, end, and meaning of the text that appears between them
- JSON (JavaScript Object Notation) – a lightweight data-interchange format – is now a new favorite language for system communication!
Systems Analysis and Design in a Changing World, 6th Edition
*
System Inputs
- Primary Objective is Error Free Input
- Use electronic devices wherever possible
- Avoid human involvement as much as possible
- If information is already available in electronic form, use it instead of re-entering information
- Validate and correct information at time and location entered
- Device Examples
- Magnetic card strip readers, bar code readers, optical character recognition, radio frequency ID tags (RFID), touch screen, electronic pens, digitizers, speech recognition
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
- Defining System Inputs Details
- Sequence Diagram
- Details for messages
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
System Outputs
- Detailed reports — reports that contain specific information on business transactions
- Summary reports — reports that summarize detail or recap periodic activity
- Exception reports — reports that provide details or summary information about transactions or operating results that fall outside a predefined normal range of values
- Executive reports — reports used by high level managers to assess overall organizational health and performance
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
System Outputs
- Internal outputs — reports or other outputs produced for use within the organization
- Types of internal reports apply here
- External outputs — reports or other outputs produced for use by people outside the organization
- Statements, notices, stockholder reports
- Higher quality, color, reflect image of organization
- Turnaround documents — external outputs that includes one or more parts intended to be returned with new data or information
- Bills
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Summary
- There are two types of interfaces – user interfaces and system interfaces
- User interfaces involve direct user interaction with the system. System interfaces require minimal or no user interaction
- The design of the user interface has a long history as human computer interaction (HCI) and relies on user-centered design, which focuses early on users, evaluates designs to ensure usability, and uses iterative development
- Metaphors are used to think about the nature of the user interface, and they include direct manipulation, desktop, document, and dialog metaphors.
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
*
Summary (continued)
- Use cases are organized into one or more menu hierarchies to arrange functionality for users
- Dialogs and storyboards are used to design the interaction for each use case based on use case flow of activates and system sequence diagrams
- System interfaces include inputs and outputs to other systems, highly automated inputs and outputs, and inputs and outputs to external databases.
- Designing system inputs involves identifying devices and mechanisms, identifying inputs and the data content, and determining the controls necessary
- Designing system outputs includes designing detailed reports, summary report, exception reports, and executive reports
- Outputs are also classified as internal, external, or turnaround
Who We Are
We are a professional custom writing website. If you have searched a question and bumped into our website just know you are in the right place to get help in your coursework.
Do you handle any type of coursework?
Yes. We have posted over our previous orders to display our experience. Since we have done this question before, we can also do it for you. To make sure we do it perfectly, please fill our Order Form. Filling the order form correctly will assist our team in referencing, specifications and future communication.
Is it hard to Place an Order?
1. Click on the “Place order tab at the top menu or “Order Now” icon at the bottom and a new page will appear with an order form to be filled.
2. Fill in your paper’s requirements in the "PAPER INFORMATION" section and click “PRICE CALCULATION” at the bottom to calculate your order price.
3. Fill in your paper’s academic level, deadline and the required number of pages from the drop-down menus.
4. Click “FINAL STEP” to enter your registration details and get an account with us for record keeping and then, click on “PROCEED TO CHECKOUT” at the bottom of the page.
5. From there, the payment sections will show, follow the guided payment process and your order will be available for our writing team to work on it.
Need help with this assignment?
Order it here claim 25% discount
Discount Code: SAVE25