SRS School Asset Management (SAM) - Amazon S3

soilkinkajouInternet και Εφαρμογές Web

2 Φεβ 2013 (πριν από 4 χρόνια και 6 μήνες)

123 εμφανίσεις

SRS
School Asset Management (SAM)


Summary:


School Asset Management

is an application that is used to manage and administer school data.
It contains 6 basic modules for in school operation and 1 module for an executive application to
consolidate data and query reports from each school. (Executive Information System).


Sch
ool Asset Management

is a combined / hybrid form 2 existing application that we refer as
SSCI (Sistem Sekolah Cerdas Indonesia) ver 3.0 and Asset Information System (AIS).
School
Asset Management

will combine features from both application thus elimina
ting redundancies as
well as inefficiencies and to further enhance the reporting system.

School Asset Management

is designed to accommodate a huge number of schools in
Indonesia for all levels, with exception to colleges and universities.

Theref
ore, an

efficient code

must be developed and to further satisfy scalability upon requirement.


Tools & References:


To assist with the development of this new breed of application, the 2 existing applications,
after

NDA execution, will be h
osted on the Internet where they will also be available for
download for further study and references. There are several documents which serve as
additional requirements

to the main SRS to accommodate and to ease processes upon
implementation. The doc
uments are as follow:

1.

SRS School Data Administration

2.

SRS Platform Support

3.

Site MAP DAS (EN).The “EN” tab is site features that have been translated into English

4.

SSCI hosted application including the source code and DB (To Be Determined)

5.

AIS
hosted application including the source code and DB (To Be Determined)


References are subject to revision to accommodate special cases and situations. It
is strongly advised for both vendor and owner to

create an online reporting system
for this particular object so both teams can streamline and troubleshoot issues that
may arise more efficiently and in a timely manner.
























E
-

Administration

:

1.

School
Profile

a.

School Directory

b.

School Facility

c.

Furniture

d.

Grant

e.

Financial Report

2.

KTSP Reference

a.

Document KTSP Reference

(Download)

b.

Introduction

c.

Curriculum Structure

d.

Calendar Academic

e.

Appendix

3.

Academic Administration

a.

Academic Data

b.

Attachment Data

4.

Administration
Data

a.

Student D
irectory

b.

Teacher D
irectory

c.

Employee D
irctory

5.

School Report Services

a.

Class Management

b.

Students Statistic

c.

Teacher Statistic

d.

Employee Statistic

6.

Web Admin

a.

Previlege

b.

Data Refence

c.

Setup

7.

Executive Information System

a.

Land and Building

b.

Students
Statistic

c.

Teacher Statistic

d.

Employee Statistic

e.

Furniture

f.

Grant


Ps : complete sitemap is attached



















Network Overview :


School Asset Management

is implemented in a distributed network architecture. The SRS
platform support document provides further details for this particular feature. Wireless OR
wired infrastructure may be employed to implement e
-

Administration.

Each remote site may OR ma
y not have an Internet connection, therefore an alternative
means of data consolidation must be prepared without disrupting the existing school day
-
to
-
day operation. A central site will be designated and will be equipped with a solid bandwidth

to acc
ommodate access requirement.
School Asset Management

will also need to be a
low bandwidth friendly application targeted for not
-
so
-
adequate remote sites.





School Asset Management

Business Process:


School Asset Management
's business process
is described below in a simplified
manner. EIS serves as the consolidation for all 6 modules. PROMIK is an
existing desktop application that contributes directly to the Academic Administration
module.






Executive Informat
ion System:


This module, as aforementioned, serves to garner individual school reports, statistics, and
data on all aspects then construct all these information into an easy to read and to visualize
reports by using graphs, charts, tables, as need
ed to satisfy the need for executives and
management levels. Schools that are connected to the Internet will operate normally, for
those who are not connected yet will use a different mean to consolidate individual school
reports to the central server as

needed. Schools will need to be able to enter data and use
application normally in their own LAN.


Additional Functions & Requirements:



Application will have a search function that is divided into 2 categories (STANDARD and
ADVANCED). This search is to
be comprehensive and capable of searching through
an existing

indexed Database or its meta data by using regular keywords. (e.g.
WIKIPEDIA search, Yahoo, Google)



Application's UI is to be user friendly for both novice or expert users.



Application is to
have standard functions such as Export, Import (Restore) that apply
comprehensively to both application and Database.



School Asset Management

it to be equipped with user manual and comprehensive
functions notes, Data Flow Diagram, and ERD for the RDBMS Database for future
troubleshoot references.










School Asset Management

EIS Consolidation Diagram:



Statement of Works


1) Assumptions

1.1 Development will be done, using


PHP as programming Language


Mysql as Database


Linux Server


Apart from
this, we will use Html, DHtml, C
SS, AJAX and other latest tools.




The following technologies will be
adopted develop the solution. :

1.

MVC Framework

2.

Ruby on Rails

3.

Apache Web Server

4.

MySQL for Database



1.2 Server will be provided by the client.


Control Panel, FTP, DB information will be provided by the client



2) Change management process/Commun
ication


Web Application Architecture Framework
. When looking to rebuild and interconnect the
proposed system we will be using the Model View Controller (MVC) web application
architecture framework. This is the most important step and first in the
remodeling of the new
updated system.


Model
-
View
-
Controller (MVC)
The architecture of the MVC application data model, user
interface, and control logic into three distinct components. This separation is beneficial
because if changes and modifications need

to be made to one of the components, they can
be done with little impact or harm to the other components.


MVC is often thought of as a software design pattern. However, MVC encompasses more of
the architecture of an application that is typical for a desi
gn pattern. Constructing an
application using MVC architecture involves defining three classes of modules domain
objects (such as student, class, attendance) that hold all the business logic and know how to
persist themselves to a database. The Controller
handles the incoming requests (such as
Save New User, Update Student Record, Show Teacher Account) by manipulating the Model
and directing data to the View. Figure below shows the conceptual model of MVC according
to the user’s viewpoint.




Use case
modeling
: The use case context diagram in Figure below shows how the
proposed system can be used with the other entities (actors, end users, system) in the
abstract. First level use cases describe the functionality of the system which results in value
adde
d to the end users (stakeholders). Use cases enable end users to get a first impression
of the intended functionality. The use case context diagram in Figure below illustrates an
example of a teacher’s interaction with the system.



The deployment of th
e proposed solution implementation will use cloud computing,
including Platform
-
as
-
a
-
Service (PaaS) for the development environment, Infrastructure
-

as
-
a
-
Service (IaaS) for hosting the proposed system , and Software
-
as
-
a
-
Service (SaaS)
as the delivery mode
l.


Figure below shows the conceptual model, which demonstrates the end user viewpoint
and the developer viewpoint in relation to the proposed system.




From our end, we will send email report on work status, everyday


except weekends and
holidays. We

expect reply/confirmation from your end, immediately, within 1 or 2 days time.
Then only, we can finish the project as said in the schedule