Benilde Student Information System v 2 0 A

Benilde Student Information System v. 2. 0 A Proposal Report by: Balaoing, Biltz, So, Sy

Overview I. II. Review of Proposal Functions and Features 1. 2. Functions vs. Features Functions and Features of Benilde SIS v. 2. 0 III. Business Requirements 1. 2. Comparison with System Requirements Business requirements of Benilde SIS v. 2. 0 IV. System Requirements 1. 2. System Requirements of Benilde SIS v. 2. 0 RUP and System Requirements V. FURPS 1. 2. FURPS + Model FURPS and System Requirements VI. Reference

Review of Proposal Company Name: De La Salle – College of St. Benilde Nature of Business: Educational Institution Student Information System Improvement (v. 2. 0) Goals How Improve load capacity of handling Higher capacity database servers requests Mobile friendly platform Responsive re-design capable of multiple device specifications Additional website functions Re-design of website using FURPS, Functions and Features

Review of Proposal: Re-design

Review of Proposal: Modernize

Proposal Problems and Recommendations Problem Recommendation Website is always down during when load is high Replace servers with a higher capacity one

Proposal Problems and Recommendations Problem Recommendation Processes are not centralized (e. g. Payment, Queue, etc. ) New Functions and Features added in website

Software Methodology Used: Rational Unified Process

Functions and Features Functions vs. Features Functions • What the programmers develop in the developing phase • What the product does • How the application should react to user's action Features • What the product has in it or what it can do • Attributes of the product • Qualities of the product • Makes the product more interesting than the others

Functions and Features Functions vs. Features of Benilde SIS 2. 0 Functionalities Features The system should be able to assign different An administrator account should be assigned to a certain privileges to different employees who would be using personnel. The administrator will be the one assigning the system. different user privileges, usernames and passwords to students and staff who would be using the system. The administrator would also be in charge of resetting passwords, re-assigning privileges, and other admin functions. In order to lessen unnecessary traffic administrators can also limit account privileges during peak times (e. g. enrollment, grades posting)

Functions and Features Functions vs. Features of Benilde SIS 2. 0 Functionalities Features The system should be able to authenticate each of the The system should be able to identify the different users that will use the system. and their position in the organization through a login mechanism similar to the past but without unnecessary page redirecting (e. g. unnecessary phone authentication) The system should be able to identify different user The system would use login credentials to know what privileges to each assigned user. privileges to give a certain user. A pre-defined privilege is assigned to a student or employee during enrollment/employment when the administrator assigns the user’s privilege. The Benilde SIS 2. 0 should be have a new payment A user must be able to choose transactions that would option redirect to a page wherein payment options are given. The system takes this information uses the accounting mechanism to receive payment via the chosen medium (e. g. Debit, credit or Pay. Pal). The system also classifies and organizes the given information through the site so that the payment would be received and given a receipt.

Functions and Features Functions vs. Features of Functionalities Benilde SIS 2. 0 Features The website system should be be able receive higher Current servers should be replaced with higher capacity traffic(compared to the legacy SIS version) servers so that higher traffic could be accommodated. The new servers would also increase capacity of the Benilde SIS 2. 0 to accommodate new functions within the system. The website should be responsive to multiple Apple, Responsive design of the website should be implemented Android and Windows mobile devices and tested within multiple devices

Business Requirements vs. System Requirements Business Requirements • Objectives or goals of the enterprise(Business) • What must be delivered to meet business needs • Requirements that the company need to have in order to stay in business • Defined as benefits of the business desires. System Requirements • Describes the behavior and information that the solution will manage • More detailed or specific • Concern the software solution to the problem stated in the business requirements. • Technical goals

Business Requirements of Benilde SIS 2. 0 • The goal of our system is to ease the traffic in the servers and make the SIS more efficient. • We aim to make our system be able to work on different devices, like phones, tablets, etc. • One of our objectives is to give SIS more functions, in which it will be a website wherein people would not need to use other websites anymore or manual processes in the school. • To meet these needs, we would need to have higher capacity database servers, designs that would fit on different devices, and analysis of the functions and features of the SIS. • The company would need to have budget for the database servers, and for the redesign and maintenance of the system.

FURPS + UNCTIONALITY • Features • Capabilities • Security

FURPS + SABILITY • Human Factors • Aesthetics • User Documentation • Training Materials • Consistency in the user interface

FURPS + ELIABILITY • Accuracy • Severity of failure • Predictability • Recoverability

FURPS + ERFORMANCE • Speed • Efficiency • Availability • Response to the user • Resource Usage • Recovery Time

FURPS + UPPORTABILITY • Maintains • Being compatible or user friendly • Testable • Adapts any environment

FURPS + • • Designs Implementation Interface Physical

System Requirements of Benilde SIS 2. 0 (using FURPS +) Functional -Redesign the functionalities of the Benilde SIS website and add new features -Higher capacity servers Usability -The interface should have a tab for each function in the program. -The design should be responsive to ALL mobile platforms Reliability -The application should be reliable even in high traffic -Down time should not be more than 3 hours Performance -For every data request sent, the program must be able to process it in less than 1 second. Supportability -Responsive website should run and be used on any Apple, Windows, Android, Linux OS computer or mobile browser supported by ASP. net, Java. Script, C#, CSS and with at least 4 gb memory ram.

FURPS +

Reference (Functions and Features) http: //english. stackexchange. com/questions/43448/functionalities-vs-features -whats-the-difference http: //programmers. stackexchange. com/questions/94164/feature-vs-function http: //inclusive. com/mmr/findings/functions_and_features. htm (Business and System requirements) http: //enfocussolutions. com/business-requirements-are-not-the-same-assystem-requirements/ https: //www. b 2 ttraining. com/business-vs-functional-requirements-who-cares/ https: //qastation. wordpress. com/2011/03/12/business-requirements-vssystem-requirements/ (Types of system requirements furps + model) http: //www. ibm. com/developerworks/rational/library/4706. html https: //businessanalysttraininghyderabad. wordpress. com/2014/08/05/what-isfurps/ http: //www. upedu. org/process/gcncpt/co_req. htm

Members Balaoing, Steven Biltz, Aralind So, Keith Sy, Robert

BENILDE SIS 2. 0 The End, Thank you!