Informatics 43 Week 3
Informatics 43 Week 3 IN4MATX 43
Popular in INTRO SOFTWARE ENGR
verified elite notetaker
Popular in Computer Programming
verified elite notetaker
This 6 page Class Notes was uploaded by SK3232 on Monday April 18, 2016. The Class Notes belongs to IN4MATX 43 at University of California - Irvine taught by NAVARRO, E. in Spring 2016. Since its upload, it has received 193 views. For similar materials see INTRO SOFTWARE ENGR in Computer Programming at University of California - Irvine.
Reviews for Informatics 43 Week 3
Report this Material
What is Karma?
Karma is the currency of StudySoup.
You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!
Date Created: 04/18/16
Inf 43 – Homework 1 Student Name: Siddhant Kasat Student Number: 11051441 Awarded Points Maximum Document Aspect Points 15 Clarity of writing (spelling, grammar, sentence construction) and Clarity of expression (flow, structure, making logical arguments). Roughly 7.5 each. 15 Introduction / Executive Summary (can be different sections or combined into one) 7.5 Application Context / Environmental Constraints (can be different sections or combined into one) 35 Functional Requirements, including usecase diagram and description of each use case. 7.5 Software Qualities and Nonfunctional Requirements 5 (+5) Other Requirements and Other Items. At least a Glossary of Terms. You can earn up to 5 points Extra Credit if you go beyond Glossary 7.5 Assumptions / Risks (can be different sections or combined into one) 7.5 Priorities / Implementation Phases; Future Directions and Expected Changes 100 TOTAL Inf 43, Homework 1 #1 of 6 Siddhant Kasat Help Me Maybe System Requirements th April 12 , 2016 Siddhant Kasat Inf 43, Homework 1 #2 of 6 Siddhant Kasat Introduction HelpMeMaybe (HMM) is an Irvine based startup company which helps tech noobs with their tech problems. Currently, they operate in Orange County and Los Angeles area and starting next week they will offer their services in New York and Washington. Presently, the company works as follows Customer calls the company and specifies the problem and a ticket is lodged. Support Executives of HMM manually find the best available Technical Assistant (TA) to solve the problem. HMM contacts TA, who tries to solves the problem on phone. Caller may also request site visit from TA if required. Caller pays HMM and then HMM pays TA. HMM are looking for someone to develop a software system which can support a mobile app and an associated website. HMM is trying to automate their system as much as possible and let users register via the app and the website. The users can log tickets via these systems. The software should automatically connect user to the ‘BEST’ TA possible. Also, onsite requests should be handled via these systems. All payments to and from HMM should be done via PayPal. Apart from all this, HMM still wants to continue their conventional method of letting users call support executives and lodge complaints. Table of Contents Overview/ Executive Summary Application Context/ Environmental Constraints Functional Requirements Software Qualities and NonFunctional Requirements Other Requirements Assumptions/ Risks Priorities/ Implementation Phases Future Directions and Expected Changes Overview / Executive Summary short, concise description main goals, key fetures, key risks/obstacles Inf 43, Homework 1 #3 of 6 Siddhant Kasat This section's audience is the nontechnical customer and user. Think of a busy executive with little time and little patience to read more than one page. It should address the goals of the system and why it is needed. Describe the major features of the system and the rationale for each (high level only, you will provide details later). Identify and describe other software, processes, hardware, people, and policies that the system may or will affect. List any assumptions made about the existing world or application context (high level only, you will provide details later). Application Context / Environmental Constraints where will the software be used, objects, proceses, software,hardware,people,etc. How do you want the UI to be? Simple/ detailed/interactive? For both mobile and Web. Which languages of programming to be used? Memory size/ hard disk space limitations? Will it be an open source? Any other software needed so that info can be passed or taken from? Browser requirements. Now you can provide more detail about “context”, for example will the application run in a business or office, home or outdoors, on a desktop, laptop, tablet, or mobile phone? Also discuss anything you might know about the operating system and “platform”, hardware constraints, design constraints (for example, what should the UI look like), software constraints (such as programming language) etc. Also mention any other software that this software will interact with. Functional Requirements This section is the heart of the specification document. It clearly describes the proposed software product, including its capabilities and attributes. Do not describe details of the user interface, such as “button in the upper left corner” or “press CtrlS to save” or “choose from a drop down box”. Instead, focus on the functionality that the system will offer. Describe the functional requirements of the system in precise detail. When possible, identify the entities (components, sections, areas of functionality) that make up the system. Characterize the properties, states, functions, and interrelationships of each entity. Since this section is the core of the requirements document, it warrants its own brief introduction. Pay careful attention to how this section is organized. Organize this section as follows: Very brief introduction to this section One usecase diagram showing all actors, use cases, and arrows for relationships Text describing each use case (can either be written in regular paragraph form, or as more of a use case template form, describing basic/alternative/exception flows, Inf 43, Homework 1 #4 of 6 Siddhant Kasat or a combination of both—see samples for examples of each). Please organize this section by user, to make it easier to grade. Remember that not all use cases will have alternative and/or exception flows. Software Qualities and Nonfunctional Requirements Generally speaking, software qualities are everything we want our software to be that is not a feature or functional requirement. The categories are usually multisyllable words that end with “ility” or at least “ty”, such as safety, security, reliability, portability, and especially usability. Discuss constraints pertaining to those qualities, if relevant, as well as speed, space, robustness, implementation bias, etc. Your audiences here are the system designers and programmers, who will probably not be in direct communication with the users. This section will help them assess tradeoffs in the system's implementation. List at least three software qualities and/or nonfunctional requirements. Other Requirements We often feel we have more to say, in other words somehow the previous two sections did not cover all requirements. This is the place to do it! Any requirements that you are aware of can be described here; you can also add diagrams or other visuals that did not fit in previous sections. At the very least you should define a Glossary of Terms with at least three terms defined. Assumptions / Risks This is the place to cover any assumptions not covered earlier. Also, list any known risks to the project from any and all perspectives, for example financial risks, business risks, legal and ethical risks, project management and development risks, etc. List at least three assumptions/risks in this section. Priorities / Implementation Phases If applicable, and following the request of the user, identify one or more subsets of the system's functionality which can or will be implemented first. One way to list priorities is to partition the requirements or use cases into “Must Have (first)”, “Should Have (second)”, and “Nice to Have (third)”. Future Directions and Expected Changes Again you are providing insight and guidance to the system designers and programmers. List at least four future directions/expected changes. Inf 43, Homework 1 #5 of 6 Siddhant Kasat Inf 43, Homework 1 #6 of 6 Siddhant Kasat
Are you sure you want to buy this material for
You're already Subscribed!
Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'