student help center srs

Upload: pankaj-kumar-jha

Post on 30-May-2018

239 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/14/2019 Student Help Center SRS

    1/20

    STUDENT HELP CENTER

    Major project

    Software Requirement Specification

    Project Guide: Project Coordinator Submitted By:

    Mrs. Ruchi Vijaywargiya Mr. Arjun Singh Parihar Pankaj Kumar JhaMr. Neeraj Mehta Sudhir Kumar

    Department of Computer ScienceS.D. Bansal College of Technology, Indore

    (www.sdbct.ac.in)July-Dec. 2009

    i | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    2/20

    Introduction....................................................................................................................................11.1 Purpose ............................................................................................................................................... 11.2 Document Conventions....................................................................................................................... 1

    1.3 Intended Audience and Reading Suggestions................................................................................... 11.3 Product Scope...................................................................................................................................... 21.4 References........................................................................................................................................... 2

    Overall Description........................................................................................................................31.5 Product Perspective............................................................................................................................. 31.6 Product Functions................................................................................................................................ 31.7 User Classes and Characteristics ........................................................................................................ 31.8 Operating Environment....................................................................................................................... 42.4.1 Software Requirement: ................................................................................................................... 4

    1.9 Design and Implementation Constraints............................................................................................. 41.10 User Documentation.......................................................................................................................... 4

    External Interface Requirements................................................................................................. 51.11 User Interfaces.................................................................................................................................. 5.................................................................................................................................................................. 5

    System Features............................................................................................................................. 91.12 Use case............................................................................................................................................. 91.13 Activity Diagram............................................................................................................................. 121.14 Sequence Diagram.......................................................................................................................... 15

    Other Nonfunctional Requirements...........................................................................................171.15 Performance Requirements............................................................................................................. 171.16 Safety Requirements....................................................................................................................... 17

    Project Plan.................................................................................................................................. 171.17 Team Members................................................................................................................................ 171.18 Time Schedule................................................................................................................................. 17

    Appendix A: Glossary..................................................................................................................18

    ii | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    3/20

    Introduction

    1.1 Purpose

    This SRS clearly suggests the requirements of the website. So it is useful to the End Users to know

    what are the requirements and recommendations of the website. Developers can use SRS to

    enhance the developed website or may develop a new website right from scratch. The SRS is also

    knowledgeable for the users to get the information about database handling and maintenance.

    1.2 Document Conventions

    Main headings:

    Font: Times New Roman 18 BOLD

    Sub Heading:

    Font: Times New Roman 14 BOLD

    Body text:

    Font: Times New Roman 12

    1.3 Intended Audience and Reading Suggestions

    End Users: End users are the ones who will be using website the most. This SRS clearly suggests

    the requirements of the web application. So it is useful to the End Users as well to know what are

    the requirements and recommendations of the website.

    Developers: The SRS is also useful to the developers who wish to develop their own website.

    They can use SRS as directly to enhance developed website or may develop a new website right

    from scratch.

    Testers: Because the website is large in size, all the testers testing the website should read SRS

    carefully to go through all the links of the website during testing.

    1 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    4/20

    1.3 Product Scope

    This project is intended to all educational organizations who want to manage the information

    about the all faculty & students. Administrator can insert, delete, and update the information of all

    faculty & students. Normal user can only retrieve the information about him. eLibrary, Onlineassessment submission, online attendance status of students, mid semester and RGPV results,

    Technical Support can be done by this website. Student & faculty can request important

    documents & download using this website.

    1.4 References

    1.4.1 Books:

    Dynamic Web Publication Second Edition Tech Media

    Mastering in ASP Mac Millan

    Beginning of Visual C# 2005 by Wrox

    Professionals of Visual C# 2005 by Wrox

    2 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    5/20

    Overall Description

    1.5 Product Perspective

    Since all the educational organizations have website which provide various information regardingtheir organization but not much helpful for student as well as faculty. All organization must to

    record all the information about student & faculty, library, attendance & results. As the data is

    huge it is tiresome to keep up the paper work for the same. Therefore it is necessary to provide an

    online web portal which helps the organizations to retain the complete record of the students &

    faculties & also provide extra services for student and faculty. There are much more website

    available to keep the information. But, there is some of the aspect which is unturned till now like

    online assessment submission, elibrary & chatting facility. Due to this problem we need to develop

    this website, which provides various services & events for students and faculty & replace all

    existing websites.

    1.6 Product Functions

    User an login with user id and password

    User can retrieve their information. User can find online assessment and notice board, online technical support

    User can see online attendance sheet

    A way in which user can request any book, magazine, journal

    User can easily download an important documents regarding their study purpose

    A way in which a student can see their midsem and rgpv results

    A way in which the various facility provided by the organization can be easily available on

    this website.

    1.7 User Classes and Characteristics

    Administrator: - He can perform all operation specified in website.

    Normal user : - He can only retrieve the information regarding to him.

    3 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    6/20

    1.8 Operating Environment

    2.4.1 Software Requirement:

    S.No Softwares

    1. MS Visual Studio 2005 For front End Design

    2. SQL Server 2000 For Database Task

    3. Adobe Photoshop CS-4 For Editing & Creating Photo

    4. Adobe Flash Professional CS-4 For Developing & Editing Flash Movie

    5. IE Tester For Testing Web Pages in Various IE

    6. Windows XP Platform for performing all these tasks

    7. IIS For running Website In a System

    2.4.2 Hardware Requirement

    S.No1. Processor Pentium IV and above2. RAM 256MB3. Processor Speed 1.6 GHz and above

    1.9 Design and Implementation Constraints

    Designer should have knowledge about technology specified in a requirement specification and

    development should be intended to requirements specified during requirement Analysis.

    1.10 User Documentation

    The solution must have enough documentation to teach the users how to use this website. The

    documentation provided in this web application should be clear enough to act as the first line of

    support for any problem. This web application will work on any windows based operating system.

    This web application needs proper maintenance and updating every day. Web application SHC is

    applicable only through internet connection.

    4 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    7/20

    External Interface Requirements

    1.11 User Interfaces

    Fig. 3.1.1 Student Help Center Home Page

    5 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    8/20

    Fig. 3.1.2 Student Help Center Registration Page

    6 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    9/20

    Fig. 3.1.3 Student Help Center Login

    7 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    10/20

    Fig. 3.1.1 Student Help Center Student Control Panel Page

    8 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    11/20

    System Features

    Functional Requirements are those that refer to the functionality of the system, i.e., what services

    it will provide to the user. Nonfunctional (supplementary) requirements pertain to other

    information needed to produce the correct system and are detailed separately.

    1.12 Use case

    4.2.1 Student Use Case

    9 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    12/20

    4.2.2 Faculty Use Case

    10 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    13/20

    4.2.3 Librarian Use Case

    11 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    14/20

    4.2.3 Administrator Use Case

    1.13 Activity Diagram

    12 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    15/20

    4.2.1 Activity Diagram of Student & Faculty

    4.2.2 Activity Diagram of Librarian

    13 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    16/20

    14 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    17/20

  • 8/14/2019 Student Help Center SRS

    18/20

    16 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    19/20

    Other Nonfunctional Requirements

    1.15 Performance Requirements

    No noticeable delays in performance. This web application performs fast result and there is no

    delay in displaying the web pages.

    1.16 Safety Requirements

    The user must have a registered account to use all facility of the website. The administrator

    account is needed to create the login id and password of normal user, and then the normal user can

    retrieve the data only.

    Project Plan

    1.17 Team Members

    Name Roll no.1

    .

    Pankaj Kumar Jha 0829cs061065

    2

    .

    Sudhir Kumar 0829cs061109

    1.18 Time Schedule

    Task Name DurationRequirement Gathering All Team Members 20 daysAnalysis All Team Members 30 daysDesign All Team Members 35 daysCoding All Team Members 30 daysTesting All Team Members 20 days

    17 | P a g ew w w . p a n k a j j h a . c o . n r

  • 8/14/2019 Student Help Center SRS

    20/20

    Appendix A: Glossary

    SQL (Structured Query Language) is a database computer language designed for managing data in

    relational database management systems (RDBMS), and originally based upon Relational Algebra.

    Its scope includes data query and update, schema creation and modification, and data accesscontrol.

    C# (pronounced "C Sharp") is a multi-paradigm programming language encompassing imperative,

    functional, generic, object-oriented (class-based), and component-oriented programming

    disciplines. It was developed by Microsoft within the .NET initiative and later approved as a

    standard by Ecma (European Computer Manufacturers Association) and ISO (ISO/IEC 23270).

    C# is one of the programming languages designed for the Common Language Infrastructure.

    The Microsoft .NET Framework is a software framework that can be installed on computersrunning Microsoft Windows operating systems. It includes a large library of coded solutions to

    common programming problems and a virtual machine that manages the execution of programs

    written specifically for the framework. The .NET Framework is a Microsoft offering and is

    intended to be used by most new applications created for the Windows platform.

    18 | P a g ew w w . p a n k a j j h a . c o . n r