Preview

Srs for School Management System

Powerful Essays
Open Document
Open Document
1668 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
Srs for School Management System
SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

FOR
Student and Unit Management System (SUMS) – Registration Module

Version 1.0

Prepared by: Taeeb Ahmad

Prepared for: Islamia model school Shabqadar fort
Preface

This document contains the Software Requirements Specification (SRS) of an Online Project Marking System for the Islamia model school shabqadar fort. The main aim of this project is to add functionality to the existing SUMS system in order to provide an online facility for managing and registering student accounts.
This document has been prepared in accordance with the IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements Specifications [IEEE 1998].
1. Introduction

This Software Requirement Specification is written accordance with the IEEE Std 830-1998 model.
1.1. Purpose

This SRS Document contains the complete software requirements for the Online Project Marking System (OPMS) and describes the design decisions, architectural design and the detailed design needed to implement the system. It provides the visibility in the design and provides information needed for software support.
1.2. Scope

Online Project Marking System is developing for Islamia model school shabqadar fort and used to replace old paper work system and PUMS. OPMS is to build upon the existing web-based project marking system PUMS in order to implement the project marking process and allocating supervisor/ideas to students. This increase in efficiency of project marking, audit trails of marking process, give feedback to student, finally, publication and email student result. It provides a mechanism to edit the online marking form which makes the system is flexible.
1.3. Definitions, acronyms, and abbreviations

IEEE The Institute of Electrical and Electronics Engineers, Inc.
OPMS Online Project Marking System
PUMS Project Units Management System
SRS Software Requirements Specification
SUMS Student and Units Management System
IMS Islamia model school
J2EE Java



References: Briggs 2005 Briggs, J. (2005). SUMS documentation. Retrieved 3rd December 2005, from http://www.tech.port.ac.uk/staffweb/briggsj/jimapp/SUMS/ IEEE 1998 IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements Specifications 1.5. Overview This document has been prepared in accordance with the IEEE Std 830‐1998, IEEE Recommended Practice for Software Requirements Specifications [IEEE 830‐1998 (1998)]

You May Also Find These Documents Helpful

  • Powerful Essays

    PROC 5000 Midterm Prep

    • 8978 Words
    • 30 Pages

    Development of specifications and a standardization program (40, 90, 119, 132, 133, 134, 136, 137, 138)…

    • 8978 Words
    • 30 Pages
    Powerful Essays
  • Powerful Essays

    Grady, Jeffrey (2010) System Management: Planning, Enterprise Identity, and Deployment, Second Edition. 1.4.2 System Requirements Analysis Page 14. Retrieved on 2-22-15 from http://wow.coursesmart.com/9781439820148/firstsection#X2ludGVybmFsX0J2ZGVwRmxhc2hSZWFkZXI/eG1saWQ9OTc4MTQzOTgyMDE0OC8xNA==…

    • 829 Words
    • 4 Pages
    Powerful Essays
  • Good Essays

    This Guideline applies to all major application projects, both new applications and upgrades of existing applications. The goals of this SDLC approach are to:…

    • 8462 Words
    • 34 Pages
    Good Essays
  • Powerful Essays

    Software Risk Management - A Practical Guide, Department of Energy Quality Managers, Software Quality Assurance Subcommittee, Reference Document SQAS21.01.00 – 1999, http://cio.doe.gov/sqas, February, 2000.…

    • 2522 Words
    • 11 Pages
    Powerful Essays
  • Good Essays

    Introduction Fasam System

    • 561 Words
    • 3 Pages

    Although this document is intended as a set of Requirements, not a design, some technical information has been included with the requirements description.…

    • 561 Words
    • 3 Pages
    Good Essays
  • Better Essays

    There are three goals to acquire in software engineering to achieve the ultimate goal, a quality application. These goals are to be reliable, efficient, and maintainable. To achieve these goals will almost certainly create a satisfied customer with a quality product. There are many methodologies to achieve this and knowing which one is the key to success. Consideration should be taken that not one size fits all in the development process. There are requirements set forth by the customer, requirements set forth by the Institute of Electrical and Electronics Engineers, (IEEE); this includes the proper documentation or artifacts. Smith Consulting should first consider and understand the reasoning for this and apply it to acquire the ultimate from them and deliver to their customers. Smith Consulting has an obligation to maintain and provide proper documentation, not only because it is required but to aid in the development process.…

    • 1626 Words
    • 7 Pages
    Better Essays
  • Good Essays

    Software Design Document

    • 854 Words
    • 4 Pages

    IEEE. IEEE Std 1016-1998 IEEE Recommended Practice for Software Design Descriptions. IEEE Computer Society, 1998.…

    • 854 Words
    • 4 Pages
    Good Essays
  • Powerful Essays

    name

    • 13159 Words
    • 53 Pages

    The content of this research paper will be our attempt to analyze and identify all the related issues and requirements…

    • 13159 Words
    • 53 Pages
    Powerful Essays
  • Powerful Essays

    Blod Bank

    • 2507 Words
    • 11 Pages

    This document is intended for developers, project coordinator, project guide, users and testers. The developer can use the document to view the analysis and design part, to understand requirements…

    • 2507 Words
    • 11 Pages
    Powerful Essays
  • Powerful Essays

    Software

    • 11653 Words
    • 47 Pages

    Software Engineering Notes Table of Contents INTRODUCTION 5 Definitions 5 Characteristics of a software Product 5 Components of software 6 Types of Software Product 6 History 6 Software Crisis:- 1965-1985 6 Software myths 7 The 4Ps of Software engineering 7 Software Development Life Cycle(SDLC) 8 Waterfall Model 8 Waterfall Strengths 9 Waterfall Deficiencies 9 When to use the Waterfall Model 10 Spiral SDLC Model 10 Spiral Model Strengths 11 Spiral Model Weaknesses 11 When to use Spiral Model 12 Prototype Model 12 Incremental model 14 Advantages of Incremental Model 15 Disadvantages Incremental Model 15 Rapid Application Development (RAD) 16 Advantages of RAD Model 16 Disadvantages of RAD Model 16 REQUIREMENTS ANALYSIS AND SPECIFICATION 17 Definitions 17 Types of Requirements 17 Requirements engineering 18 Requirement engineering Process 18 DESIGN PHASE 20 Architecture 20 Implementation Plan 21 Critical Priority Analysis 21 Performance Analysis 21 Test Plan 22 Modularity 23 SOFTWARE PROJECT MANAGEMENT 25 THE MANAGEMENT SPECTRUM 25 CHARACTERISCTIC OF AN EFFECTIVE PROJECT MANAGER 26…

    • 11653 Words
    • 47 Pages
    Powerful Essays
  • Powerful Essays

    This template can be used to create Software Requirements Specifications that conform to IEEE Standard 830-1993.…

    • 1560 Words
    • 7 Pages
    Powerful Essays
  • Good Essays

    Student Database

    • 1680 Words
    • 7 Pages

    This document has been prepared in accordance with the IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements Specifications [IEEE 1998].…

    • 1680 Words
    • 7 Pages
    Good Essays
  • Powerful Essays

    References: 1. 2. 3. 4. Appell B. Putting in a Replacement for Controbloc P20 AT Chooz B. Nuclear Eng.Int.1992; 37:45-58. Craigen, D., Gerhart, S., and Ralston T. Case Study: Darlington Nuclear Generating Station. IEEE Software 1994; 11: 30-32. Hughes, G., Boettcher D.B. Developments in Digital Instrumentation for Nuclear Electric’s (UK) Power Plant. Nuclear Energy 1993; 32: 41-52. Modarres, M. Functional Modeling of Complex Systems Using a GTST-MPLD Framework. Proceeding of the 1st International Workshop of Functional Modeling of Complex Technical Systems, Ispra, Italy 1993 IEEE 1058.1 IEEE Standard for Software Project Management Plan. 1987 IEEE 1074 IEEE Standard for Developing Software Life Cycle Process 1995. IEEE 730.1 IEEE Standard for Quality Assurance Plans. 1989 IEEE 730.2 IEEE Guide to Software Quality Assurance Planning. 1993 IEC 880. Software for Computers in the Safety Systems of Nuclear Power Stations 1986. IEEE 121.9 IEEE Standard for Software Maintenance 1992. IEEE 1228. IEEE Standard for Software Safety Plans 1994. IEEE 1012. IEEE Standard for Software Verification and Validation Plan 1986. IEEE 828. IEEE Standard for Software Configuration Management Plans. 1983. IEEE 1042. IEEE Guide to Software Configuration Management. 1987. IEEE 830. IEEE Guide to Software Requirements Specification. 1984. IEEE 1016. IEEE Recommended Practice for Software Design Descriptions. 1986. Schweiggert, F., Schoitsch, E. Qualitatssicherung in der Software, OCGComputerakademie, Seminarunterlagen. 1985. Lawrence J. D. Software Reliability and Safety in Nuclear Reactor Protection Systems. NUREG/CR-6101 UCRL-ID-114839 , Lawrence Livermore National Laboratory. 1993. NUREG-0800: HICB-BTP-14, Guidance on Software Reviews for Digital ComputerBased Instrumentation and Control Systems (Draft). 1998.…

    • 2673 Words
    • 11 Pages
    Powerful Essays
  • Better Essays

    How to Write Srs

    • 2752 Words
    • 12 Pages

    In this article I explain the major sections of a typical Software Requirement Specification document. I also provide a generic SRS template which can be customized for your project needs.…

    • 2752 Words
    • 12 Pages
    Better Essays
  • Satisfactory Essays

    for higher education courses. Its basic objectives are to extend their reach to geographically scattered…

    • 6892 Words
    • 28 Pages
    Satisfactory Essays

Related Topics