srs updated checked

SAINT COLUMBAN COLLEGE

PAGADIAN CITY

COLLEGE OF COMPUTER STUDIES

Software Requirements Specificationfor

SCC Information Disseminator: A system for disseminating of Information through Local Area Network and E-Bulletin.

IT Group 2

“Mach5”

Almonte, Jelly Mae P.

Baltazar, Jessaneth B.

Ching Carl Angelo L.

Ihara Jr, Noel B.

Salazar, Ragde Ama T.

SignatureThe following signature indicates approval of the enclosed Software Requirements Specifications Document.

Noel B. Ihara Jr.Project manager

Jelly Mae. P. Almonte Carl Angelo L. Ching System Analyst Programmer

Ragde Ama T. Salazar Jessanth B. Baltazar Quality Assurance Documenter

Mr. Neil Owen B. Jandugan Adviser/Editor

Submitted and accepted by:

Mr. Philipcris C. Encarnacion , MCS CCS Dean

Change History

Table 1

Revisions Date Reason For Changes Person who

suggested the

changes

Group Name June 16, 2014 Team Celeron change its name to

Mach5 because the meaning of

Celeron itself does not suit the team’s

characteristics.

Jessaneth B. Baltazar

(Documenter)

Title Name September 8, 2014 The title of the study was changed

from E-Bulletin to SCC Newscast

System to make it more suitable with

the proposed system.

Ragde Ama T. Salazar

(QA Tester)

Preface October 24, 2014 The sentence construction of the

preface was improved.

Mrs. Janus A. Naparan

(Client)

Overview October 24, 2014 The sentence construction of the

overview was improved.


(Client)

Product

Perspective

October 24, 2014 The description of the product

perspective was changed and a block

diagram presentation was added.

Mr. Francis Rebo

Alegre

(Panel)

Product

Functions

October 24, 2014 The terminologies of the product

functions were changed.

Mr. Francis Rebo

Alegre

(Panel)

Mr. Neil Owen B.

Jandugan

(Adviser)

User

Characteristics

October 24, 2014 The sentence construction of the 2.2

User Characteristics was improved.

Mr. Francis Rebo

Alegre

(Panel)

Constraints October 24, 2014 The constraints were changed and

some uncontrolled instances that the

system may encounter were

discussed.


(Client)

User Interfaces October 24, 2014 The user interface was further

discussed with a description and some

of the user interfaces were changed.


(Client)

Mr. Neil Owen B.

Jandugan

(Adviser)

Hardware

interfaces

October 24, 2014 The hardware interface was further

discussed with a description and more

hardware components were added.


(Client)

Mr. Francis Rebo

Alegre

(Panel)

Software

interfaces

October 24, 2014 The software interface was further

discussed with a description.

Mr. Francis Rebo

Alegre

(Panel)

Use case

diagram

October 24, 2014 The use case diagram was revised

and some terminologies of the entities

were changed.


(Client)

Performance

Requirements

October 24, 2014 The performance requirements was

revised and the performance of the

system were specifically discussed

according to the range of time.

Mr. Francis Rebo

Alegre

(Panel)

Mr. Neil Owen B.

Jandugan

(Adviser)

Design

Constraints

October 24, 2014 The design constraint was revised and

was organized according to the

operating system and processor.

Mr. Neil Owen B.

Jandugan

(Adviser)

Index October 24, 2014 The index was revised and some

words were added in the list.

Mr. Neil Owen B.

Jandugan

(Adviser)

Preface

This document, Software Requirements Specification (SRS), is created to document the software requirements for the SCC Newscast System, as described in the 3 sections: (1) Introduction; (2) Overall Description; and (3) Specific Requirements, of this document.

The purpose of the study SCC Newscast System is to enhance the way the school disseminate information to the students, faculty and staff and administration within the school premises. The system offers the college a clear view of displaying information through electronic board or TV screens. It also provides reliable information to the public viewers since all the information/announcement entered in the system is properly reviewed by the authorized user of the system. The system was designed and developed with the use of the tools and technology that are already available and accessible for several years to the public for use in both commercial and personal projects across the globe.

Table of Contents

Signature....................................................................................................................................................................................2Change History..........................................................................................................................................................................3Preface........................................................................................................................................................................................6Table of Contents.......................................................................................................................................................................7List of Figures............................................................................................................................................................................8List of Tables..............................................................................................................................................................................91. Introduction.........................................................................................................................................................................10

1.1. Purpose........................................................................................................................................................................................... 101.2. Scope.............................................................................................................................................................................................. 101.3. Definitions, Acronyms and Abbreviations......................................................................................................................................111.4. References...................................................................................................................................................................................... 111.5. Overview........................................................................................................................................................................................ 11

2. Overall Description.............................................................................................................................................................132.1. Product perspective........................................................................................................................................................................132.2. Product functions............................................................................................................................................................................142.3. User characteristics.........................................................................................................................................................................142.4. Constraints.....................................................................................................................................................................................142.5. Assumptions and dependencies......................................................................................................................................................14

3. Specific Requirements .......................................................................................................................................................152.1.External interface requirements.......................................................................................................................................................15

3.1.1. User interfaces......................................................................................................................................................................153.1.2. Hardware interfaces..............................................................................................................................................................152.1.1.Software interfaces.................................................................................................................................................................16

3.2. Functional requirements.................................................................................................................................................................163.2.1. Use case ............................................................................................................................................................................... 16

3.3.Performance Requirements..............................................................................................................................................................173.4.Design Constraints.......................................................................................................................................................................... 173.5. Software system attributes..............................................................................................................................................................173.6. Other requirements.........................................................................................................................................................................17

4. Appendixes..........................................................................................................................................................................185. Index....................................................................................................................................................................................19

List of Figures

Figure 1: Block diagram……………………………………………………………………………………………………...13

Figure 2: Use case diagram………………………………………………………………………………………………….16

List of Tables

Table 1: Change History………………………………………...…………………………..………………………………3-5Table 2: Definitions, Acronyms and Abbreviations………………………………………...………………...………...….12

Software Requirements Specifications SCC Newscast System

Document Version: 3.0Published Date: 27 October 2014

1. Introduction

The mode of disseminating information way back in history was just simple. They relied on the bulletin boards to display announcements or used posters to inform the public. Others preferred to use the print media or the broadcast. This has changed considerably because society has seen the impact of combining the traditional ways of informing others, instead of individually using it by applying and engaging into technology.

Currently, in a fast changing world, the manner of conveying or sharing information has revolutionized. The synergy of the technological advancements plus the power of the computer is a very vital tool that enhances tasks and provides convenience for all. It has brought forth major innovations. By now, Saint Columban College follows the trend but it is still in the process of reinventing its system to accommodate new ways to achieve excellence.

The researchers plan to take advantage of their technological knowledge and the breakthrough by proposing a system that gives better, easier and efficient way of disseminating information. The researchers plan to enhance the system to accommodate daily updated activities and announcements in the aid of multimedia and networking technology.

1.1. Purpose

The purpose of this document is to present a detailed description of SCC Newscast System. It will explain the purpose and functional features of the system, along with interface details and design constraints, what the system will do. This document is intended for the Information Office of Saint Columban College and the developers of the system will propose this system to the department dean for its approval.

The group proposes a system that is more advantageous and efficient to use, allows user to post or read information accessed by computers connected in the network, a user-friendly system that could help spread information inside the campus faster. The proposal will be a great solution to the problem and a new beginning to introduce improvements in terms of spreading information effectively. The system has a templates where the user can select his/her desired style in posting the information and set other settings, color has time frame to make sure that the information are exactly on time.

1.2. Scope

SCC Newscast System provides reliable information to the students, faculty, staff and alumni of Saint Columban College. With the help of the system, the school can deliver up-to-date announcements, news, school activities or any information that is related or maybe applicable to the institution.

This system is limited to the students, faculty and staff within the premises of Saint Columban College because all information being freely provided are mostly related to the school activities and the system will also be implemented in the school premises only through local area network.

All the information displayed on the application requires human intervention; this means an appropriate person tasked to this would review information content before adding and publishing its content for public view.

of 19



1.3. Definitions, Acronyms and Abbreviations

Table 2

Term Definition

Database Collection of all the information monitored by this system.

Software Requirements Specification

A document that completely describes all of the functions of a proposed system and the constraints under which it must operate. For example, this document.

User A person using a common system.

IEEEThe Institute of Electrical and Electronics Engineers (IEEE) is a membership organization that includes engineers, scientists and students in electronics and allied fields.

Newscast Television broadcast of new reports.

1.4. References

• IEEE. IEEE STD 830-1998 IEEE Recommended Practice for Software Requirements Specifications. IEEE Computer Society, 1998.

• SRS Sample1 –Sample6.

• 830-1984 — IEEE Guide to Software Requirements Specifications. 1984.

• 830-1993 — IEEE Recommended Practice for Software Requirements Specifications. 1994.

• 830-1998 — IEEE Recommended Practice for Software Requirements Specifications.

1.5. Overview

The project focuses on the development and creation of the SCC Newscast System for our client. This document has 5 major sections:

• Introduction provides an overview of the entire SRS document and the product being specified.

• Overall Description provides overview detail of the entire document.

• Specific Requirements provides the specifications of the system.

• Appendixes provides a section or table of additional matter at the end of a book or document.

• Index provides list of words or phrases and associated pointers to where useful material relating to that heading can be found in the document.

of 19



of 19



2. Overall Description

2.1. Product perspective

The SCC Newscast System will involve the following offices: (1) Information Office; (2) College of Computer Studies; (3) College of Business Education; and (4) College of Teachers Education Arts and Sciences. It will help the information personnel to bring up-to-date news, activities, and announcements through networking with the involved departments. It is user friendly and provides a variety of templates to choose from to suit each announcement to be published.

Figure 1: Block Diagram

of 19



2.2. Product functions

These are the system product functions:

1. Sending And Receiving of Announcement Request2. Notification To Server For New Request3. User’s Authentication4. Adding, Editing, Deleting, Retrieval of Announcement

2.3. User characteristics

The user must have the following qualifications:

1. Must be Computer Literate2. Must be at College Level3. Knowledgeable in Microsoft Office4. Have an authorized account to assure the security of the system.

2.4. Constraints

The constraints of the SCC Newscast system are the following:

1. It will not work if there is no network or there is a problem on the network connection.

2. The system will only display the same output on all monitors.

3. The budget provides a forecast of revenues and expenditures in the project. Without proper budget plan, the development can exceed or over spend which will lead into higher production cost.

4. Large video file might cause delay in displaying the video announcement.

5. The system’s output display relies on the splitter, therefore if the splitter will be damaged or might malfunction, there will be no announcements that will be displayed on the monitors.

2.5. Assumptions and dependencies

It is expected that the system has a security measures embedded like user authentication process to insure the stability of the system. The system can allow accounts to be created specifically for authentication purposes to track record of the information encoded by the user. The said assumptions and dependencies is a way to illustrate the possible requirements needed and to clarify what will be the chanced issues.

of 19



3. Specific Requirements

2.1. External interface requirements

External interface requires that the software must support human manipulation of the software products, in cases when the user of the system operates through a display (e.g. required screen formats) the inputs must be relative to the outputs. The external interface comprises the following interfaces: (1) user interfaces; (2) hardware interfaces; and (3) software interfaces.

3.1.1. User interfaces

The user interfaces are the portion of an interactive computer system that communicates with the user and any aspects of the system that is visible to the user. It includes the following:

• Authentication in which users/members and administrators will input their username and their password.

• Registration form for signing up.

• Server/Admin page that includes manage announcement, notifications, templates, skins and message box.

• Client page which includes propose announcement, notification and message box..

3.1.2. Hardware interfaces

Hardware interfaces are may be purchased components or reused from another application and being developed for subsystems outside and which this hardware application must interact.

The hardware interfaces of SCC Newscast are the following:

1. Desktop/Laptop Computers

Recommended Specifications:

• At least 300 gigabytes of HDD

• At least Dual Core Processor

• At least 2GB installed RAM

• Video card: NVIDIA NVS 310 Dual Display

• Internet Connection and local area network

• Operating system : windows 7, 8, and 8.1

2. Splitter

3. LAN

Includes: UTP Cable, RJ-45 and Router

4. TV Screen

of 19



2.1.1. Software interfaces

Software interfaces are the languages and codes that the applications use to communicate with each other and with the hardware.

The software interfaces of SCC Newscast are the following:

• Microsoft Visual Studio

• MySql

• Windows media player

3.2. Functional requirements

3.2.1. Use case

Use Case Diagram illustrates the actions undertaken by the users (administrators) in accessing the system.

of 19

DSA OFFICE, 10/27/14

send announcement request. Info personnel/administrator….check spelling of announcement…input announcement (specify or delete input emergency announcement)…change server respond to approve announcement



3.3. Performance Requirements

The SCC Newscast should take a maximum of 20 seconds for authentication; and 3 minutes for uploading photos and videos. For bigger file sizes of photos and videos, it may take 5 to 7 minutes to upload.

3.4. Design Constraints

The design constraints of SCC Newscast are the following:• It will not play unsupported video file format.• It will display different video or graphical text output for LCD screen with different dimension.• It will display pixilated video output for 3gp video file format.

3.5. Software system attributes

The software system attributes are the following:• Reliability: The SCC Newscast System will not fail to load the announcements.• Availability: It is available at the three departments and also at the Information Office.• Maintainability: Easy to maintain and to handle events.• User friendly: menus, tool bars, buttons and all the things in the SCC Newscast system would be

easy to understand by the server and client user. • Security: It has authentication system to prevent unauthorized access. All those confidential data in

database will be managed by the administrator only and the client user of SCC Newscast can’t be able to access and modify the database.

3.6. Other requirements

This specifies the normal and special operations required by the client such as: 1. Local area network and internet connection. 2. Client version of SCC Newscast software installed.

This specifies the normal and special operations required by the server such as:1. Local area network and internet connection.2. Server version of SCC Newscast software installed.3. Computer unit that has VGA or HDMI port.

of 19



4. Appendixes

Pre-Approval Sheet Title of the Research:

SCC Newscast System

Date Presented:

July 15, 2014

Group Name:

MACH5

Members:Noel B. IharaJelly P. AlmonteRagde Ama T. SalazarCarl Angelo L. ChingJessaneth B. Baltazar

Brief Description of the ProjectThe SCC Newscast System is more advantageous and easier to use since it allows user to post or read information, and send announcement requests to server from identified work station. It user friendly and will help disseminate information inside the campus faster. The system has templates where the user can select his/her desired style in posting the information (e.g. changing the color of the fonts). It has time frame to ensure that the information are disseminated on time.

APPROVED BY:

Mr. Philipcris C. Encarnacion,MCS Dean

Mr. Neil Owen B. JanduganAdviser

of 19



5. Index

Authentication, 13, 14, 16

Database, 11, 16

Information, 6, 10, 11, 12, 13, 16, 17

Interfaces, 3, 14, 15

Network, 10, 12, 13, 14, 16

Newscast, 3, 6, 10, 11, 12, 13, 14, 15, 16, 17

Product, 3, 11, 12, 14

Registration, 14

Security, 13, 16

Software, 2, 3, 6, 12, 15, 16, 17

System, 2, 3, 6, 11, 12, 13, 14, 15, 16, 17, 18

Templates, 11, 13, 15, 18

User, 3, 4, 11, 12, 13, 14, 16, 17, 18

of 19

srs updated checked

Technology

neil owen

proposed system

janduganadviser indexoctober

scc newscast system

sentence construction

naparanclient overviewoctober

ragde ama t

ihara jr