annotated-96E5BA2096E6A3.doc

pdf

School

Troy University, Troy *

*We aren’t endorsed by this school

Course

3332

Subject

Computer Science

Date

Dec 6, 2023

Type

pdf

Pages

Uploaded by HighnessSquirrelMaster1003

 Q4.1 Identify and briefly describe four types of requirements that may be defined for a computer-based system. (3 points)  Requirements for a computer-based system define what the system is expected to do, how it should perform, and what constraints or limitations it must adhere to. Here are four types of requirements commonly defined for computer-based systems:Functional Requirements ， Non-Functional Requirements ， User Requirements ， System Constraints and Compatibility Requirements   Q4.2 Discover ambiguities or omissions in the following statement of requirements for part of a ticket-issuing system: (3 points)   While the provided statement of requirements for the ticket-issuing system is relatively concise, there are still some potential ambiguities and omissions that should be addressed:User Interaction Flow ， Credit Card Validation ， Error Handling ， Security and Data Protection 。 To create a more comprehensive and unambiguous set of requirements, it's advisable to work closely with stakeholders, including end-users, and to consider various scenarios and edge cases to ensure that all aspects of system functionality and behavior are covered  Q4.3 Rewrite the above description using the structured approach described in this chapter. Resolve the identified ambiguities in a sensible way. (3 points)  User Initiation and Destination Selection:  When the user activates the machine by pressing the start button, the system shall display a menu of potential destinations.  The system shall prompt the user to select a destination from the displayed menu.  Additionally, the user shall be asked to specify the type of ticket required (e.g., one-way, round-trip).  Credit Card and PIN Input:  After selecting a destination and ticket type, the system shall request the user to input their credit card information.  The credit card input shall include the card number and expiration date.  Following the credit card input, the system shall request the user to input their personal identification number (PIN).  Transaction Logging and Audit Trails:  The system shall maintain a log of all transactions, including timestamps, user actions, and transaction outcomes.  Audit trails shall be securely stored for audit and troubleshooting purposes.  Transaction Cancellation  The system shall allow users to cancel a transaction at any point before the ticket is issued.  If a user cancels a transaction, any charges made to their credit card shall be reversed promptly. 

 Q4.6 Suggest how an engineer responsible for drawing up a system requirements specification might keep track of the relationships between functional and non-functional requirements (3 points)  Keeping track of the relationships between functional and non-functional requirements is crucial for creating a well-structured and comprehensive system requirements specification. Here are some suggestions for how an engineer can effectively manage these relationships:Documentation Structure,Cross-References,Dependency Notations,Annotations and Comments,Version Control and Change Management.  Q4.10 You have taken a job with a software user who has contracted your previous employer to develop a system for them. You discover that your company’s interpretation of the requirements is different from the interpretation taken by your previous employer. Discuss what you should do in such a situation. You know that the costs to your current employer will increase if the ambiguities are not resolved. However, you also have a responsibility of confidentiality to your previous employer. (3 points)  In a situation where you've taken a job with a software user, and you discover that your current company's interpretation of the requirements is different from your previous employer's interpretation, you are faced with a challenging ethical and professional dilemma. Here's what you should consider doing:Understand the Differences,Consult with Colleagues,Raise Concerns Internally,Engage with the Client,Ethical Considerations,Seek Mediation or Third-Party Assistance. Chapter 5  Q 5.1. Explain why it is important to model the context of a system that is being developed. Give two examples of possible errors that could arise if software engineers do not understand the system context. (3 points)  Modeling the context of a system being developed is a crucial step in the software engineering process because it helps software engineers understand the broader environment in which the system operates. Failing to model the context adequately can lead to several errors and challenges in system development. Here are two examples of possible errors that can arise if software engineers do not understand the system context   Q 5.2. How might you use a model of a system that already exists? Explain why it is not always necessary for such a system model to be complete and correct. Would the same be true if you were developing a model of a new system? (3 points) Using a model of an existing system can be valuable in various scenarios, including understanding, analyzing, and improving the system. Here's how you might use a model of an existing system:Understanding and Documentation,Analysis and Optimization,Testing and Validation,Legacy System Migration 

  Q 5.3. Propose a set of use cases that illustrates the interactions between a doctor, who sees patients and prescribes medicine and treatments, and the Mentcare system (3 points)  Use Case 1: Doctor Login   Actor: Doctor  Description: The doctor logs into the Mentcare system using their credentials (username and password) to access patient information and perform medical tasks.  Preconditions: The doctor must have valid login credentials.  Basic Flow:  The doctor navigates to the Mentcare system's login page.  The doctor enters their username and password.  The system verifies the credentials.  If the credentials are valid, the doctor gains access to the system.   Q 5.6. Look carefully at how messages and mailboxes are represented in the email system that you use. Model the object classes that might be used in the system implementation to represent a mailbox and an e-mail message (3 points) Mailbox Attributes: mailboxID: A unique identifier for the mailbox. owner: The user who owns the mailbox. messages: A collection of email messages stored in the mailbox. Methods: addMessage(message): Adds an email message to the mailbox. removeMessage(message): Removes an email message from the mailbox.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

getUnreadMessages(): Returns a list of unread email messages in the mailbox. Email Message Class: Attributes: messageID: A unique identifier for the email message. sender: The sender of the email. recipients: The list of recipients (can be one or more). subject: The subject of the email. body: The content or body of the email. timestamp: The date and time the email was sent. read: A flag indicating whether the email has been read by the recipient. Methods: getSender(): Returns the sender of the email. getRecipients(): Returns the list of recipients.   Q 5.9. Draw a State diagram of the control software for the camera on your mobile phone. Ignore the flash if you have one on your phone. (3 points) State: Idle - Description: The initial state when the camera application is launched Transitions: 1. Event: User taps "Open Camera" - Action: Transition to the "Camera Preview" state. State: Camera Preview - Description: The camera is active, showing a live preview of the camera feed. Transitions:

2. Event: User taps "Capture Photo" - Action: Capture a photo and transition to the "Photo Preview" state. 3. Event: User taps "Switch to Video Mode" - Action: Transition to the "Video Recording" state. 4. Event: User taps "Access Settings" - Action: Transition to the "Camera Settings" state. State: Photo Preview - Description: Display the captured photo to the user. Transitions: 5. Event: User taps "Save Photo" - Action: Save the photo and return to the "Camera Preview" state.

Related Documents

M3_Ch16HomeworkQuestions(1).docx

Ch14ReplacementHWFile(1).docx

DOS lab.docx

HandsOnProjectWeek3.docx

ITNW 2312 Lab 4.1.1b Troubleshooting Single-Area OSPFv2 and OSPFv3.docx (2).docx

ITNW 2312 Lab 3.1.1a Basic EIGRP for IPv4.docx

CIT 352 Chap 07 Hands-On Projects.docx

HandsOnProject14-2.docx

CIT 352 Chap 06 Hands-On Projects.docx

Chap10HandsOnProjects.docx

Quiz_ Classroom Teaching in a Digital World.pdf

HandsOnProject11-2.docx

Recommended textbooks for you

Database Systems: Design, Implementation, & Manag...

Computer Science

ISBN:9781305627482

Author:Carlos Coronel, Steven Morris

Publisher:Cengage Learning

Principles of Information Systems (MindTap Course...

Computer Science

ISBN:9781305971776

Author:Ralph Stair, George Reynolds

Publisher:Cengage Learning

Fundamentals of Information Systems

Computer Science

ISBN:9781305082168

Author:Ralph Stair, George Reynolds

Publisher:Cengage Learning

Fundamentals of Information Systems

Computer Science

ISBN:9781337097536

Author:Ralph Stair, George Reynolds

Publisher:Cengage Learning

Systems Analysis and Design (Shelly Cashman Serie...

Computer Science

ISBN:9781305494602

Author:Scott Tilley, Harry J. Rosenblatt

Publisher:Cengage Learning

Principles of Information Systems (MindTap Course...

Computer Science

ISBN:9781285867168

Author:Ralph Stair, George Reynolds

Publisher:Cengage Learning

SEE MORE TEXTBOOKS

Recommended textbooks for you

Database Systems: Design, Implementation, & Manag...
Computer Science
ISBN:9781305627482
Author:Carlos Coronel, Steven Morris
Publisher:Cengage Learning
Principles of Information Systems (MindTap Course...
Computer Science
ISBN:9781305971776
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning
Fundamentals of Information Systems
Computer Science
ISBN:9781305082168
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning
Fundamentals of Information Systems
Computer Science
ISBN:9781337097536
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning
Systems Analysis and Design (Shelly Cashman Serie...
Computer Science
ISBN:9781305494602
Author:Scott Tilley, Harry J. Rosenblatt
Publisher:Cengage Learning
Principles of Information Systems (MindTap Course...
Computer Science
ISBN:9781285867168
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning