University Management System

Conceptualization

Introduction
Scope of the UMS E2E Solution Architecture Sample Workflow/s Implementation Phases

Project Structure
Sample Project Plan Implementation Models Next Steps

Target Audience: Senior Stake Holders, Delivery Managers, Project Managers

Scope of the UMS

Functional Scope
University Management System with the following key modules* Admission Management Accounts Management Student and Staff Management Department and Facilities Management Campus Management Hostel Management Canteen Management Library Management Course & Examination Management General Campus Management
*Actual scope will be dependent on the detailed scoping exercise.

Scope of the UMS contd

Technical Scope
The following are the KEY* technical considerations for the University Management Solution 24x7 University Web Site Internal/External Content Management Facilities to the University Department/Function wise Intranets Smart Card based Identity for Students and Staff Bar-coded Technology for Library Management Fully Featured Administration Module Controlled Access to the University Sites/Features based on Security Management System Advanced Search Facilities Daily Automated Batch Reports Audit Log, University Calendar, End of Day Processing, Maker-Checker, Alerts etc. Centralized Hosting
*Actual scope will be dependent on the detailed scoping exercise.

End 2 End Solution Architecture

*Actual Architecture will be dependent on the detailed design and scope.

End 2 End Solution Architecture Contd

Zone
Intranet

Published Intranet Sites

http://delta http://delta/library http://delta/hostel http://delta/accounts https://intranet.delta.com https://intranet.delta.com/library https://intranet.delta.com/hostel https://intranet.delta.com/accounts

Default

Zone
Intranet

Team Sites
http://teams/sites/Team1 http://teams/sites/Team2 http://teams/sites/Team3 https://teams.delta.com/sites/Team1 https://teams.delta.com/sites/Team2 https://teams.delta.com/sites/Team3

Default

Zone
Internet

Internet Site
http://www.delta.com

*Actual Architecture will be dependent on the detailed design and scope.

End 2 End Solution Architecture

Module Level Architecture representing various modules. Layers, Security Layer, Search Engine, EOD, Report Engine, Separate Sites, Administrator Module, Intranet, Extranet, Content Publishers, Separate items , Alert Engine, Smart Card Integration, Bar Code integration, Auditing

*Actual scope will be dependent on the detailed scoping exercise.

End 2 End Solution Architecture

Key Activities -Data Migration (Explanation) - Barcoding - Smart Card Based Identity

*Actual scope will be dependent on the detailed scoping exercise.

End 2 End Solution Architecture

Use Cases and Sequence Diagrams for Some Sample Scenarios Library, Hallticket Printing Content Publishing

*Actual scope will be dependent on the detailed scoping exercise.

End 2 End Solution Architecture

Sample Sites and their breakup/Seperation Different Types of User Access Rights Rights Sample Reports, Sample Alerts

*Actual scope will be dependent on the detailed scoping exercise.

End 2 End Solution Architecture

Sample Table Designs

*Actual scope will be dependent on the detailed scoping exercise.

Implementation Phases
Initial Agreement on the Solution Model Initiate High Level Scoping Exercise and Signoff

Detailed Requirements and Signoff

Planning

Infrastructure Planning

Site/Content Design Planning

Development Planning

Database Design

SMS Planning

Execution Milestone Integration

Mockrun

Execution

Testing

Deployment & SIT UAT, Performance & Penetration Testing Cutover Planning Staging & Production Deployment

Bug Fixes & Releases

Closure

Post Production Support

Project Structure
Customer
Data Migration & Cleansing Team

Business Analyst Team Requirements Study SRS Preparation Scope Signoff Process Flow Diagrams Support other teams

UMS Delivery Manager

Infrastructure Team
Hardware Requirements Sizing and Procurement Network/Security Deployment

Testing & Release Team Test Case Preparation Test Scenario Execution Configuration Mgmt Release Mgmt

Application Team Site/Database Design Site Creation Authoring & Publishing Custom Development

Project Structure Contd

UMS Delivery Manager

Application Team

Library Management Team

Hostel Management Team

Canteen Management Team

Student Management Team

Resource Pool
Database Developers Business Analysts Site Designers Application Developers

Implementation Model Pipeline Approach...

Time Line
Preparation

Legacy Modules Study

Design/Build

Code Drop 1 Code Drop 2 Code Drop n

New Module Study

Scoping/Signoff

Design/Build

Code Drop n+1

New Module Study

Scoping/Signoff

Design/Build

Code Drop m

SIT UAT

Implementation Model Pipeline Approach...

Advantages
Parallel execution of both Legacy and New Modules Parallel SIT & UAT Shorter Implementation Timelines

Disadvantages
More Resources Required both on the Development and Customer side Bug Fixing and Testing difficult to streamline Development Cycle, Release and Configuration Management Difficult Highly dependent modules will have to be taken up in one set Possible Design Revisits Very Effective and Strong Programme Management body required.

Implementation Model Phased Approach...

Time Line
Preparation

Legacy Modules Study

Design/Build

Code Drop 1 Code Drop 2 Code Drop n

New Module Study

Scoping/Signoff

Design/Build

Code Drop n + x

SIT

UAT
Iterations (New Timelines)

Go Live

Implementation Model Phased Approach...

Advantages
Some Parallel activity for both Legacy and New Modules Limited Resources More Controlled Approach hence result in High Quality Better Design Approach Option of Go-Live with Limited Releases Ease of Handling Requirements, Release and Configuration Management

Disadvantages
Longer Implementation Cycles Possible Non-Utilization of Resources in some phases Very Effective and Strong Programme Management body required. Cost may be higher

Risk Management RAID Logs...

R - Risks A Actions

I Issues
D - Dependencies

Sample Risk Record

Date Raised Raised By Description Risk Category Phase Identified in Mitigation Plan Assigned To Closed Date Status

Next Steps
Agreement of the High-level Solution Decision on Technology Client Team Formation Scope Agreement End to End Cost Assessment Team Building Detailed Project Planning & Implementation

Next Steps
Risk Mgmt - purpose - backup up Project plan