Cis 331 Week 4 Case Study 1: Software Requirement Specification

In: Business and Management

Submitted By Laynebaril
Words 376
Pages 2
CIS 331 Week 4 Case Study 1: Software Requirement Specification
Click Link Below To Buy:

http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/
Or Visit www.hwcampus.com

Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you:
1. Create a Software Requirement Specification (SRS) that includes the following:
1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided.
2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided.
3. A detailed requirement specification written in structured natural language.
2. Structure and present the requirements in a logical and consistent manner.
3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements:
• Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.
• Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length.
• Include charts or diagrams created in Visio or an equivalent such as Dia. The completed diagrams / charts must be imported into the Word document before the…...

Similar Documents

Software Requirement Specification

...Software Requirements Specification Template CptS 322—Software Engineering 9 February 2005 The following annotated template shall be used to complete the Software Requirements Specification (SRS) assignment of WSU-TC CptS 322. The instructor must approve any modifications to the overall structure of this document. Template Usage: Text contained within angle brackets (‘’) shall be replaced by your project-specific information and/or details. For example, will be replaced with either ‘Smart Home’ or ‘Sensor Network’. Italicized text is included to briefly annotate the purpose of each section within this template. This text should not appear in the final version of your submitted SRS. This cover page is not a part of the final template and should be removed before your SRS is submitted. Acknowledgements: Sections of this document are based upon the IEEE Guide to Software Requirements Specification (ANSI/IEEE Std. 830-1984). The SRS templates of Dr. Orest Pilskalns (WSU, Vancover) and Jack Hagemeister (WSU, Pullman) have also be used as guides in developing this template for the WSU-TC Spring 2005 CptS 322 course. Software Requirements Specification Lead Software Engineer Prepared for WSU-TC CptS 322—Software Engineering Principles I Instructor: A. David McKinnon, Ph.D. Spring 2005 Revision History Date Description Author Comments Document Approval The following...

Words: 1662 - Pages: 7

Cis 518 Week 6 Case Study 1 Generative Software Development

...CIS 518 Week 6 Case Study 1 Generative Software Development Click below link for answer http://workbank247.com/q/cis-518-week-6-case-study-1-case-study-1-generativ/3603 http://workbank247.com/q/cis-518-week-6-case-study-1-case-study-1-generativ/3603 Case Study 1: Generative Software Development This assignment consists of two (2) sections: a written report and a PowerPoint presentation. You must submit the two (2) sections as separate files for the completion of this assignment. Label each file name according to the section of the assignment it is written for.  Section 1: Written Report Read the case study titled, “Generative Software Development” located in Chapter 5 of the textbook. Then, imagine a situation where your organization is considering a generative development process for its new line of software products. You are asked to present a written report to the organization’s CIO about generative software development and its usage. Write a five to six (5-6) page paper in which you: 1. Define in your own words, what is meant by generative software development, and describe how it contrasts with other software development processes. 2. Describe the benefits of applying the generative development in an organization. 3. Explain the challenges of implementing the generative software development process in an organization. 4. Describe how the challenges faced during the implementation of the generative software development process can be overcome. ......

Words: 517 - Pages: 3

Cis 524 Week 2 Case Study 1

...A++PAPER;http://www.homeworkproviders.com/shop/cis-524-week-2-case-study-1/ CIS 524 WEEK 2 CASE STUDY 1 CIS 524 Week 2 Case Study 1, Case Study 1: User Interfaces Due Week 2 and worth 90 points Early user interfaces were designed with little or no consideration for the end user. This was largely due to technical and hardware limitations. The poor interface design required a specific skill set for users and limited the mass appeal of computers. Modern interfaces are much more user friendly. Theo Mandel wrote about the five (5) golden rules of interface design. Read Mandel’s article located at http://www.theomandel.com/docs/Mandel-GoldenRules.pdf. Write a four to five (4-5) page paper in which you: 1. Describe three (3) interfaces you interact with on a daily basis. 2. Analyze each interface you identified in Question one (1) and assess how it adheres to Mandel’s five (5) golden rules. 3. Suggest two (2) changes for each interface to achieve a more user-friendly design and justify your suggestion. 4. Provide three (3) screen shots for each interface. Note: These screen shots should be labeled and appear in the appendix of the case study. These pages are not included in the page requirement for the assignment. 5. Use at least three (3) quality resources in this assignment. Note: Wikipedia and similar Websites do not qualify as quality resources. Your assignment must follow these formatting requirements: Be typed, double spaced, using......

Words: 362 - Pages: 2

Cis 524 Week 4 Case Study 2

...A++PAPER;http://www.homeworkproviders.com/shop/cis-524-week-4-case-study-2/ CIS 524 WEEK 4 CASE STUDY 2 CIS 524 Week 4 Case Study 2, CIS 524 Week 4 Case Study 2 Case Study 2: Design Process Due Week 4 and worth 90 points You have recently started your own software design company. You discover that your local DMV is looking to build a system that will allow receptionists to check customers in quickly. They would like for the system to allow customers to self-check-in during busy times, but have receptionists check customers in the rest of the time. Your company puts a bid in for the project and wins. Read the article located at http://www.bcs.org/upload/pdf/ewic_hc07_lppaper18.pdf. Write a four to five (4-5) page paper in which you: 1. Suggest the prototyping technique you would use for this system and support your rationale. 2. Create a management plan containing eight to ten (8-10) stages for proper design of such a system. 3. Explain each stage of the management plan and justify your rationale. 4. Estimate the length of time it will take to complete each stage of the management plan. 5. Compare and contrast the self-check-in interface with the interface a receptionist would use. 6. Use Microsoft Visio or an open source alternative, Dia, to create a total of two (2) graphical representations of your proposed interfaces, one (1) for the self-check-in and one (1) for the receptionist. Note: The graphically depicted solution is not......

Words: 466 - Pages: 2

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional......

Words: 376 - Pages: 2

Cis 331 Week 4 Case Study Assignment

...CIS 331 Week 4 Case Study Assignment http://hwguiders.com/downloads/cis-331-week-4-case-study-assignment CIS 331 Week 4 Case Study Assignment There are many possibilities you can take when dealing with an SS. A SRS is basically an organization understands of the customer or potential client’s system requirements and dependencies at a particular point in time prior to any actual design or even change development work. This is known as a two-way insurance policy that makes sure that both the client and the organization understand the other’s requirements from a certain perspective at a given point in time. In this essay I will create a SRS of a hotel managements system. I will also give you examples of an SRS and explain things such as the description, the function, and the specifications. User & System Requirements With this system come user requirements. These are certain requirements that will help gain access to the SRS for the hotel. It will also be broken down into specific categories. For example; the software that will most likely be used is the oracle. While some of the user requirements will be login credentials, reservations, check ins, payments and room service. The external requirements will include things such as a computer or laptop, keyboard, mouse, and a printer. As for the hardware requirements, this system will most likely be running on windows by Microsoft. Functional and Nonfunctional Requirements Most of the functional requirements...

Words: 267 - Pages: 2

Cis 331 Week 8 Case Study 2

...CIS 331 week 8 case study 2 http://hwguiders.com/downloads/cis-331-week-8-case-study-2 CIS 331 week 8 case study 2 After reading “A Patient Information System for Mental Health Care”, I found it necessary that I explain how this system works for the best. In this essay I will explain things such as, the overall architecture for a kind of system. I will explain why this pattern and architecture is important. There will also be key features explained such as architecture patterns, how these patterns can be applied ad implemented and even the shortcomings associated with the architecture. I will also present a UML diagram explaining how the process will work. Patient Information System We use the patient information system to support mental health care. This is a medical information system that maintains information about patients suffering from mentalhealth problems and the treatments that they have received while in recovery. Most mental healthpatients do not require dedicated hospital treatment but need to attend specialistclinics regularly where they can meet a doctor who has detailed knowledge oftheir problems. To make it easier for patients to attend, these clinics are not justrun in hospitals. They may also be held in local medical practices or communitycenters. Mental Health Care-Patient Management System The MHC-PMS (Mental Health Care-Patient Management System) is an informal system that is intended for use in clinics. It makes use of a centralized......

Words: 283 - Pages: 2

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional......

Words: 376 - Pages: 2

Software Requirements Specification Document

...Software Requirements Specification for Mountain Bank Cell Phone App Version 5.0 approved CS455/Techs2ATee May 11, 2015 Table of Contents 1. Introduction 1 1.1 Purpose 1 1.2 Document Conventions 1 1.3 Intended Audience and Reading Suggestions 2 1.4 Project Scope 2 1.5 References 3 2. Overall Description 6 2.1 Product Perspective 6 2.2 Product Features 6 2.3 User Classes and Characteristics 7 2.4 Operating Environment 7 2.5 Design and Implementation Constraints 7 2.6 User Documentation 8 2.7 Assumptions and Dependencies 8 3. System Features 9 3.1 Establish Secure Session 9 3.1.1 Description and Priority 9 3.1.2 Stimulus/Response Sequences 9 3.1.3 Functional Requirements 9 3.1.4 Secure Session Test Script 10 3.2 Login 12 3.2.1 Description and Priority 12 3.2.2 Stimulus/Response Sequences 12 3.2.3 Functional Requirements 12 3.3 View Balances 13 3.3.1 Description and Priority 13 3.3.2 Stimulus/Response Sequences 13 3.3.3 Functional Requirements 13 3.4 View Transaction History 14 3.4.1 Description and Priority 14 3.4.2 Stimulus/Response Sequences 14 3.4.3 Functional Requirements 14 3.5 Transfer Funds 15 3.5.1 Description and Priority 15 3.5.2 Stimulus/Response Sequences 15 3.5.3 Functional Requirements 15 3.5.4 Funds Transfer between Accounts Test Script 16 3.6 Deposit 20 3.6.1 Description and Priority 20 3.6.2 Stimulus/Response Sequence 20 3.6.3 Functional Requirements 20 3.6.4 Successful Deposit Test......

Words: 13282 - Pages: 54

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional......

Words: 376 - Pages: 2

Software Requirement Specification

...< Project scenario name > Software Requirements Specification Version < X.0> < team Name > < Scenario Name > Software Requirements Specification Version < X.0> Team Guide:( Faculty Guide’s Name ) Members:(Team members name) College Name: Department: State: / Page 1 < Project scenario name > Software Requirements Specification Version Revision History Date Version 1.0 2.0 Description Synopsis Synopsis Author / Page 2 < Project scenario name > Software Requirements Specification Version X.0 Table of Contents Description 1.0 Introduction 1.1 1.2 1.3 1.4 1.5 1.6 Purpose Scope Definition, Acronyms, and Abbreviations References Technologies to be used Overview Page No. 2.0 Overall Description 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 Product Perspective Software Interface Hardware Interface Product Function User Characteristics Constraints Architecture Design Use Case Model Description / Page 3 < Project scenario name > Software Requirements Specification Version X.0 2.9 Class Diagram ........................................................................ Sequence Diagram s ............................................................... 2.10 Database Design .................................................................... 2.11.1 2.11.2 ER Diagram ............................................................... Schema......

Words: 739 - Pages: 3

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional......

Words: 376 - Pages: 2

Software Requirements Specification

... | | | | | | | |Software Engineering | |MedPulse | |Software Requirements Specification | | | | | | | | ...

Words: 3076 - Pages: 13

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional......

Words: 376 - Pages: 2

Software Requirement Analysis and Specification

...Abstract:-Software requirement analysis is a method to find out the requirements form the user to develop software. Software requirement analysis and specification also include the types of user requirements and the methods by which developer team can elicit the user requirement and develop suitable software for the user. Introduction:- ➢ Requirement analysis: - Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications. Requirements analysis is an important aspect of project management. Requirements analysis involves frequent communication with system users to determine specific feature expectations, resolution of conflict or ambiguity in requirements as demanded by the various users or groups of users, avoidance of feature creep and documentation of all aspects of the project development process from start to finish. Energy should be directed towards ensuring that the final system or product conforms to client needs rather than attempting to mold user expectations to fit the requirements. Requirements analysis is a team effort that demands a combination of hardware, software and human factors engineering expertise as well as skills in dealing with people. ➢ Software requirement analysis: - The success of any new......

Words: 2585 - Pages: 11