This action might not be possible to undo. Are you sure you want to continue?
Group Name: <place your group name here>
MUAZZAM YOUNUS AYEEN MUHAMMAD M. USMAN AUN MUHAMMAD 15790 15497 14058 14000 firstname.lastname@example.org email@example.com Usmanidreesi7@gmail.com Aunmahammad12@gmail.com
Instructor: Course: Lab Section: Date:
MUHAMMAD SHOAIB SOFTWARE ENGINEERING LR-9 25-MARCH-2013
...Software Requirements Specification for <Project> Page ii Contents <IN THIS TEMPLATE YOU WILL FIND TEXT BOUNDED BY THE “<>” SYMBOLS.............. .....................III THE EXPLANATIONS PROVIDED BELOW...................... IF YOU HAVE ANY QUESTIONS REGARDING THIS DOCUMENT PLEASE REFER TO THE MINITHERMOSTAT SRS EXAMPLE ON THE COURSE WEB-SITE..................................................... BUT MERELY............................. MAKE SURE TO DELETE ALL OF THE COMMENTS BEFORE SUBMITTING THE DOCUMENT.................................................. OPTIONAL SECTIONS WILL BE EXPLICITLY MARKED AS OPTIONAL. THESE COMMENTS THAT ARE IN BLACK ARE INTENDED SPECIFICALLY FOR THAT COURSE...............................................3 3 SPECIFIC REQUIREMENTS.......>............ IT IS BASED ON THE IEEE REQUIREMENTS AND WAS ADAPTED SPECIFICALLY FOR THE NEEDS OF SOFTWARE ENGINEERING 3K04/3M04 COURSES....................................................... THIS TEXT APPEARS IN ITALICS AND IS INTENDED TO GUIDE YOU THROUGH THE TEMPLATE AND PROVIDE EXPLANATIONS REGARDING THE DIFFERENT SECTIONS IN THIS DOCUMENT..........................III 1 INTRODUCTION......................................... THERE ARE TWO TYPES OF COMMENTS IN THIS DOCUMENT..............8 4 OTHER NON-FUNCTIONAL REQUIREMENTS................................................... Date Completed 00/00/00 ........................ I.... This table does not need to be filled in whenever a document is touched...........E..............................10 5 OTHER REQUIREMENTS................ FAILURE TO DO SO WILL RESULT IN MARKS DEDUCTIONS.................... PLEASE....11 Revisions Version Draft Type and Number Primary Author(s) Full Name Description of Version Information about the revision..........................................................1 2 OVERALL DESCRIPTION................... only when the version is being upgraded............... THESE COMMENTS THAT ARE IN BLUE ARE MORE GENERAL AND APPLY TO ANY SRS............................................... DO NOT COVER ALL OF THE MATERIAL................ YOU MUST INCLUDE THEM IN YOUR VERSION OF THE DOCUMENT........................................................... MOST OF THE SECTIONS IN THIS TEMPLATE ARE REQUIRED SECTIONS.............................. THE GENERAL NATURE OF THE INFORMATION YOU WOULD USUALLY FIND IN SRS DOCUMENTS..............
> . This text appears in italics and is intended to guide you through the template and provide explanations regarding the different sections in this document. do not cover all of the material.Software Requirements Specification for <Project> Page iii <In this template you will find text bounded by the “<>” symbols. These comments that are in black are intended specifically for that course. the general nature of the information you would usually find in SRS documents. i. make sure to delete all of the comments before submitting the document. Optional sections will be explicitly marked as optional. Please. Failure to do so will result in marks deductions. but merely. Most of the sections in this template are required sections. The explanations provided below.e. There are two types of comments in this document. These comments that are in blue are more general and apply to any SRS. If you have any questions regarding this document please refer to the MiniThermostat SRS example on the course web-site. It is based on the IEEE requirements and was adapted specifically for the needs of Software Engineering 3K04/3M04 courses. you must include them in your version of the document.
Suggest a sequence for reading the document.4 Definitions. e. Describe the scope of the product that is covered by this SRS. and documentation writers (In your case it would probably be the “client” and the professor). TO DO: Write 1-2 paragraphs describing the purpose of this document as explained above. including acronyms and abbreviations. Make sure to describe the benefits associated with the product. marketing staff.> . testers. TO DO: 1-2 paragraphs describing the scope of the product.5 Document Conventions <In general this document follows the IEEE formatting requirements. such as fonts or highlighting that have special significance. Use italics for comments. TO DO: Please provide a list of all abbreviations and acronyms used in this document sorted in alphabetical order.1 Document Purpose <Identify the product whose software requirements are specified in this document. or 12 throughout the document for text.> 1. project managers.> 1. Acronyms and Abbreviations <Define all the terms necessary to properly interpret the SRS. such as developers. Sometimes. You may wish to build a separate glossary that spans multiple projects or the entire organization.> 1. particularly if this SRS describes only part of the system or a single subsystem. including relevant benefits. users. beginning with the overview sections and proceeding through the sections that are most pertinent to each reader type.. Describe what the rest of this SRS contains and how it is organized. objectives. TO DO: Describe any standards or typographical conventions that were followed when writing this SRS.g. etc. For Section and Subsection titles please follow the template. it is useful to divide this section to several sections. Use Arial font size 11.Software Requirements Specification for <Project> Page 1 1 Introduction <TO DO: Please provide a brief introduction to your project and a brief overview of what the reader will find in this section.> 1. and just include terms specific to a single project in each SRS. Document text should be single spaced and maintain the 1” margins found in this template.2 Product Scope <Provide a short description of the software being specified and its purpose. including the revision or release number. Naming Conventions.3 Intended Audience and Document Overview <Describe the different types of reader that the document is intended for. and goals.> 1. Formatting Conventions.
6 References and Acknowledgments <List any other documents or Web addresses to which this SRS refers. or a vision and scope document.> . These may include user interface style guides. An example citation guide is posted for you on the website.Software Requirements Specification for <Project> Page 2 1. TO DO: Use the standard IEEE citation guide for this section. contracts. use case documents. standards. system requirements specifications.
The customization wizard will help the customer to choose a suitable hardware and software configurations. A team of technical experts known as ‘wizards’ will help the users in selecting the proven combinations. Accurate determination of arrival time for both national and international shipments is guaranteed. International trading is another salient feature of the Marvel online. Internal to Enterprise External to Enterprise Customer/End user (Web Clients) Administrator E-Commerce System Credit card system Inventory System Delivery System . customize and then purchase. Various payments apart from the consumer market.Software Requirements Specification for <Project> Page 3 2 Overall Description The Marvel Online plans to provide the customers an easily accessible environment which will enable them to access the different ranges of products that they can view. International delivery means that the system needs to check for delivery restrictions for the destination address. To understand the product better various viewing options such as 3D models and virtual modeling are also included. the e-store also incorporate an end-to-end architecture and communicate automatically with the suppliers for an excellent inventory control and overall cost reduction.
.Software Requirements Specification for <Project> Page 4 2.3 Customer Support Marvel online will offer unmatched customer service not available elsewhere.1 Product Perspective 2. delivering. Marvel Online should be able to assist customers in the browsing. and returning service. The goal is to provide a total shopping experience for a variety of customers.2 Users and Characteristics Following characteristic are as under. Marvel Online will have a set of wizards implemented at every stage of shopping which will guide the customer. buying. 2. selecting. This is one of the major issues which are keeping buyers at distance from online shopping.
10 Large number of Payment options. 2.5 Security Security of transaction is an important concern in Online shopping . International sales will allow processing of e-commerce transaction throughout the world. This addresses the goal of making e-commerce shopping experience similar to retail shopping experience. This is particularly important in the technological sector.7 Marketing and Advertisement.12 Design and Implementation Constraints • • The project must commence on July 2013 The e-store must not take business away from its retail partners. 2. The statistical information will be used in calculating the discount to each user. Good encryption algorithms and use of SSL feature should be used .Also beyond certain purchase limit Marvel online will offer free shipment as well. . and statistical information to be use for marketing and manufacturing analysis. The checking of Action includes selecting desired product. as parts prices tend to depreciate quickly.This includes safeguard against the disclosure of customers’ private information. Marvel Online accepts third party payments as well. Occasional e-marketing is necessary to attract potential customers and increase total sales.4 Product Configuration as per user needs ‘Build to need’ is a unique feature which allows customers to configure a variety of configurable Marvel products. Real time inventory allows for easy and efficient restock of needed parts and minimizing upkeep. 2. The goal is to make Marvel ecommerce website usable for majority of the population. Customers should be able to pick and choose parts to configure their products. The Marvel Online will guarantee the delivery of purchased products on the promised date. completing payment option.6 International Trade.11 Fast and efficient Shipping. This unique feature allows customer retention and more shopping rate. 2.9 Support Real Time Inventory Allows manufacturing segment of Marvel Electronics to minimize inventory up keep. 2.8 Customer Profile (Data Mining) The Marvel Online allows the collection of customers’ opinion feedbacks. Real time inventory allows for price to quickly update to market trends. The customer can also keep track of the shipment . 2. The goal is to create an ecommerce that can evolve to meet changing needs.Software Requirements Specification for <Project> Page 5 2. This feature solves the need for customization of stock products. Also Marvel Online’s wizards will select the most compatible product configurations.The Marvel Online should make shopping experience safe. Allows the promotion of sales and announcements to customers. and specifying delivery methods as well as checking the legal intricacies in shipment of product to that country. 2. The Marvel Online will allow the customers to shop online with variety of payment options. shopping preferences. 2.
it must not interfere with current business operations. 2. 7. • Detail Description of the Item This section provides a detailed description about specific function of the product and the techniques in using those functions. • Result This section describes expected results.3 Installation Guides. 2. If the user is unable to perform the installations the user can contact the customer support or browse through the online support. A discussion of compatibility issues with earlier releases and a "What's New" section will also be available in the Readme file. 7. or if these published modules should be revised. Configuration. Read Me Files All Marvel online products will be provided with complete installation guides. Installation guides. functions. online help. 7.13 User Documentation The Marvel Online plans to better serve their customers by providing them with information about the product they have purchased through documentation manuals. The manual format may be altered if another format is more suitable for the particular project. This section describes the purpose of each document and the information it provides. including the specific high-level functions performed by the product are described in this section.4 Labelling and Packaging . configuration guidelines. and step-by-step procedures for access and use. and operations.Software Requirements Specification for <Project> Page 6 • While the project is under development. Feedback from users will be taken from time to time to determine whether additional modules should be developed. In addition to these guides and manuals a user can always call the customer support whenever he has trouble setting up or installing. capabilities.2 Online Help The Marvel website will contain an online user’s guide that will explain all of the features of the Marvel products and instructions on how to use them. contingencies and alternate modes of operation. Known bugs and workarounds for various systems will be given in the Readme file. The web site will also provide online support wizards for more complex features like custom configurations. • Purpose and scope This section provides a description of the purpose and scope of the User Manual • General Description An overview of the item's capabilities. All of the online documentation will be indexed and fully searchable. The user manual contains a description of the item its functions. and Readme files. Examples will be shown to get the correct output. and configuration and Read Me files.14 User Manual The User Manual contains all essential information for the user to make full use of the information about the item.
labeling and packing.Software Requirements Specification for <Project> Page 7 The guidelines provide standards for insulated packaging. We assume that there is a smooth supply of products as per the requirement from the manufactures. The e-store provides accurate delivery time for its products. storage volumes. 2. Seamlessly The support for real time inventory already exists in marvel infrastructure . The e-store does not intend to lose business at its partner retail chain. as well as standard shipping procedures. The e-store operates internationally.15 Assumptions and Dependencies • • • • • • • • We have not scoped the price of the hardware required to run the system. Delivery of the product to the customer depends upon the external agency which is given the responsibility of product delivery. • Standard shipping procedures The arrival of items in different countries. Labelling and Packaging : Manufacturers are required to indicate packed volumes and weights of items. The e-store intends to serve different classification of customers. Some of the important points from these standards are as follows: • Insulated Packaging: Packaging must be designed to assure safe temperatures during the period of transportation • Storage Standards. their subsequent clearance through customs and their transport are the most critical stages in an item shipment.
TO DO: The least you can do for this section is to describe in words the different User Interfaces and the different screens that will be available to the user. operating systems (Windows? Linux? Etc…).3 Software Interfaces <Describe the connections between this product and other specific software components (name and version). network server communications protocols. standard buttons and functions (e.g. but provide 1-2 paragraphs were you will outline the major communication standards. Define the software components for which a user interface is needed.1 User Interfaces <Describe the logical characteristics of each interface between the software product and the users. For example. including databases.> 3. TO DO: The previous part illustrates some of the information you would usually include in this part of the SRS document.. and so on. Identify the data items or messages coming into the system and going out and describe the purpose of each. TO DO: Do not go into too much detail.Software Requirements Specification for <Project> Page 8 3 Specific Requirements 3. Describe the services needed and the nature of communications. error message display standards.1 External Interface Requirements 3. If the data sharing mechanism must be implemented in a specific way (for example. In case you have more than one hardware interface divide this section into subsections. such as FTP or HTTP.1. This may include sample screen images. Define any pertinent message formatting.1. TO DO: Please provide a short description of the different hardware interfaces. but it will be usually included in this part as well. data transfer rates. To make things simpler. and synchronization mechanisms. the nature of the data and control interactions between the software and the hardware. Identify data that will be shared across software components. including e-mail. specify this as an implementation constraint. screen layout constraints. any GUI standards or product family style guides that are to be followed. If you will be using some special libraries to communicate with your software mention them here. tools. Cancel) that will appear on every screen. if you decide to use encryption there is no need to . You are not required to specify what protocols you will be using to communicate with the hardware. electronic forms. you are only required to describe the specific interface with the operating system. Identify any communication standards that will be used.4 Communications Interfaces <Describe the requirements associated with any communications functions required by this product.> 3. and integrated commercial components. libraries. will be rewarded by extra marks. Those who will be able to provide optional Graphical User Interface screenshots.1.1. This may include the supported device types. and so on. Specify any communication security or encryption issues. web browser. use of a global data area in a multitasking operating system).2 Hardware Interfaces <Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system.> 3.
Since sometimes we will not be able to specify completely the behaviour of the system by just State Diagrams.> .1 Use Case View <A use case defines a goal-oriented set of interactions between external actors and the system under consideration.3 Behaviour Requirements 3.2 where you have specified the general functional requirements. TO DO: Brake the functional requirements to several functional areas and divide this section into subsections accordingly.1. but rather. TO DO: Provide a use case diagram which will encapsulate the entire system and all possible actors.2 Functional Requirements < Functional requirements capture the intended behavior of the system.Software Requirements Specification for <Project> Page 9 specify the exact encryption standards. > 3. Provide a detailed list of all product operations related to these functional areas.3. For more information please refer to your UML guide and the MiniThermostat SRS example file. Do not include detailed use case descriptions (these will be needed when you will be working on the Test Plan). specify the fact that the data will be encrypted and name what standards you consider using. but make sure to include a short description of what every use-case is. who are the actors in your diagram. This section is the direct continuation of section 2.3. tasks or functions the system is required to perform. you should list in detail the different product functions with specific explanations regarding every function. we use use-cases to complete what we have already started in section 3. This behavior may be expressed as services. 3. Here.
Define any safety certifications that must be satisfied. Define any user identity authentication requirements. and again you need to be creative here. TODO: Provide at least 5 different performance requirements based on the information you collected from the client. clarify the relative preferences for various attributes.> 4. that you do not just write “This software shall be maintainable…” Indicate how you plan to achieve it. TODO: Use subsections (e.. and usability. state them here and explain their rationale. etc…) provide requirements related to the different software quality attributes.> . Any transaction will not take more than 10 seconds. correctness. availability. and verifiable when possible. portability.Software Requirements Specification for <Project> Page 10 4 Other Non-functional Requirements 4.1 Reliability. Base the information you include in these subsections on the material you have learned in the class. on your ABM related research. Refer to any external policies or regulations that state safety issues that affect the product’s design or use. & etc…Do not forget to include such attributes as the design for change. quantitative.3. Some to consider are: adaptability.g.1 Performance Requirements <If there are performance requirements for the product under various circumstances. • Describe briefly what level of security is expected from this product by your client and provide a bulleted (or numbered) list of the major security requirements.3 Software Quality Attributes <Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. reusability. etc…> 4. You may need to state performance requirements for individual functional requirements or features. to help the developers understand the intent and make suitable design choices. Define any safeguards or actions that must be taken. such as ease of use over ease of learning. or harm that could result from the use of the product.3. At the least. flexibility. robustness. 4. Make such requirements as specific as possible. TODO: • Provide at least 3 different safety requirements based on your interview with the client or. damage. maintainability. but it is the mere minimum and it will not receive the full marks. interoperability.2 Safety and Security Requirements <Specify those requirements that are concerned with possible loss. Specify the timing relationships for real time systems. as well as actions that must be prevented. Make sure. Please note that you need to include at least 2 quality attributes.2 Portability. testability. 4. reliability. For example you can say “1. Write these to be specific.
legal requirements.Software Requirements Specification for <Project> Page 11 5 Other Requirements <This section is Optional. reuse objectives for the project. internationalization requirements.> . Add any new sections that are pertinent to the project. Define any other requirements not covered elsewhere in the SRS. and so on. This might include database requirements.
Software Requirements Specification for <Project> Page 12 Appendix A – Data Dictionary <Data dictionary is used to track all the different variables. In the table. states and functional requirements that you described in your document. include the description of these items as well as all related operations and requirements.> . inputs and outputs in a table. state variables (and their possible states). Make sure to include the complete list of all constants.
your group activities.Group Log <Please include here all the minutes from your group meetings. and any other relevant information that will assist the Teaching Assistant to determine the effort put forth to produce this document> .Software Requirements Specification for <Project> Page 13 Appendix B .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.