teaching allocation system (tas) - … · web viewthis project explains and set a solution to...
TRANSCRIPT
TEACHING ALLOCATION SYSTEM (TAS)
Ongaranathan Vinokaran
[Deakin University, Australia]
Software Project Plan
Abstract
This project based on Teaching Allocation System (TAS) which is capable of making allocation of lecturer and module, Time allocated for module to be synced automatically. Many functionalities and features are included in TAS system which is going to be a new step in the innovation of database system. As of IOT (Internet Of Everything) says internet rules the world in near future, all the manual system has to be systemized into online to get access from anywhere and part of the world.
Project includes scope, project development model, estimation of size, cost estimate, planning and scheduling, risk analysis these topics are subdivided into sub topics to explain and describe the need of this project.
Table of Contents1.0 Project Description..............................................................................................................................4
1.1 Project scope.....................................................................................................................................4
1.2 Objectives..........................................................................................................................................4
1.3 System Statement of Scope...............................................................................................................4
1.3.1 General Requirements................................................................................................................4
1.3.2 Extended Requirement...............................................................................................................5
1.3.3 Extended Enhancement..............................................................................................................5
1.4 System Context..................................................................................................................................6
1.5 Project constraints.............................................................................................................................6
1.5.1 Critical success criteria................................................................................................................6
1.5.3 Critical success factors................................................................................................................6
1.6 Project Deliverables...........................................................................................................................7
1.7 Project Boundaries............................................................................................................................7
2.0 Project Development Model................................................................................................................8
2.1 Characteristic of Project....................................................................................................................8
2.2 Project Life Cycle Model....................................................................................................................8
2.3 Selection of Waterfall Model.............................................................................................................9
3.0 Project Estimates...............................................................................................................................10
3.1 Estimation Techniques Applied and Results....................................................................................10
3.2 Estimation Technique: Constructive Cost Model (CoCoMo)............................................................11
3.3 Total Cost Calculation......................................................................................................................12
4.0 Planning and Scheduling...................................................................................................................13
4.1 Project Resources............................................................................................................................13
4.2 Task List...........................................................................................................................................15
4.3 Task Network...................................................................................................................................16
4.4 Work Break down Structure (WBS)..................................................................................................17
4.5 Gannt chart......................................................................................................................................19
4.5.1 Snapshot of Gannt chart figures...............................................................................................19
4.5.2 Resource allocation...................................................................................................................24
5.0 Risk Analysis................................................................................................................................25
5.1 Introduction.....................................................................................................................................25
5.2 Risk identification and analysis........................................................................................................25
5.3 Probability-impact of risk.................................................................................................................27
5.4 RMMM plan.....................................................................................................................................30
6.0 Appendix......................................................................................................................................33
6.1 14 point questionnaire....................................................................................................................33
6.2 CoCoMo Value chart........................................................................................................................34
6.3 Probability impact grid of tasks.......................................................................................................34
6.4 Gannt chart with resource...............................................................................................................35
1.0 Project Description
1.1 Project scopeThis project explains and set a solution to overcome the problem of current manual teaching allocation system which allocated through excel. Automatic or semi-automatic system will have a solution for complexity in allocating units to lecturer according to their priority and previous experience. Features of this system includes allocation of units for lecturer which is performed by centralized server, On line submission for their teaching preference, Adjustment and confirmation for teaching units for upcoming year through on-line and report generation.
1.2 ObjectivesThe purpose of this system to be created and implemented is a huge step in allocating modules to lecturers in accordance to their preference. It opens a new era in database system of university infrastructure. Set objectives and goals allows the project to success. The goals of TAS are:
To minimize the time frame wasted in allocating units for lecturer To compare and contrast allocation of units and lecturer priority To avoid the complexity created as a result of working manually
1.3 System Statement of Scope
1.3.1 General Requirements
Following are the general requirement for TAS:
Allow system administrator to set up accounts for academic staff members, head of institute and teaching administrator;
Allow academic staff to select and change their teaching preferences before the submission due date;
Store teaching preferences submitted by academic staff; Allocate teaching units to academic staff automatically or semi-automatically; Modify and adjust allocation results; Verify whether the allocation task is finished; Notify academic staff of the teaching allocation results via e-mail; Allow academic staff to confirm allocated teaching units; Verify whether all allocations are confirmed, i.e. the allocation task is finalized; Generate allocation reports for all individual staff; Generate reports of allocation statistics; Suspend and terminate accounts by the head of institute; Add/remove teaching units; Edit details of teaching units (e.g. contact hours, number of lectures/pracs); Store and manage information required for teaching allocation and account management;
Perform system backup and restore.
Critique: Bounding is a critical element of the project scope and the project plan. It would be great idea to “bound” all basic need for this system such as: capacity of the database, number of images and text usage in the database, formats of reports supported document types specification
1.3.2 Extended Requirement
User Friendly system
Consideration in user friendly system is crucial part of any system which deals with low bandwidth usage, straight through access
Database Administrative system
This allows university to administrate and communicate with any lecturer through online 24*7. Proper creation and maintenance makes life easier.
Online help
Help menu and video footage of using this database will be uploaded and updated if any upgrading happens in future.
Training
Proper training will be provided for the university staff after launch of the product.
1.3.3 Extended Enhancement
Palm Pilot Integration
Palm pilot integration & online record access are the enhancement applied to this concept as its more suits with the requirement, the team and client both agree on doing the palm pilot integration. From the design point of view, online record access has a major security risk, which the team has little or no experience on it. Palm pilot integration on other hand, needs only programming, which can be (and will be) achieved by the team. We also suggest to theDEQ that they can make the online record request to be the next semester’s project.Before we decide on what kind of Palm Pilot we use, the team and the client have explored several options.Comment: An implied risk is noted in blue above. This should be further addressed inthe risk management section of the plan.
Improvement in database
The database which is going to be developed not optimized to the level of user friendly. It will be resolved when project grows up.
1.4 System ContextSystem is capable of handling complex request and auto optimizing when it’s needed. As this system has multiple users concurrent connection will be an issue for implementation. Addition to this it’s an initial approach for this kind of system which can be developed further and manipulated in other parts of the world [flamelabe.de, 2009].
1.5 Project constraints“
1.5.1 Critical success criteriaThe project success is measured and defined by stakeholders of Hope health based on the factors below given
Total budget of the project will not exceed the initial budget, the project will be funded by university of Deakin
Projected duration will be adjusted only by 15 days at any cost, no delays and triggers will be created
1.5.3 Critical success factorsThe factors which can affect the success of the project given below:
Completion of the project on time and within budget and scope” Project team will be committed and motivated throughout the lifecycle of the project” Effective use of stakeholder management, risk management, change management,
communication channels, stakeholder reviewing as well as business competency level will be monitored and utilized throughout the project to increase the probability of successful outcome of the project”
1.6 Project Deliverables“
As project grows in each and every phase many outputs will be created due to the action taken or performed. TAS deliverables are:
Scope Statement Detailed plan for the project {Work breakdown structure along with gannt chart} Progress Reports Issues Reports Weekly Meeting Notes Feedback from developers, sponsor and other heads involved within this project Final product “ Highly trained staff
[techrepublic.com, 2007]”
1.7 Project Boundaries“
Project boundaries creates the limitation for any system. Some of the boundaries of the project is listed below:
Pop-up menu for any updates in the patient discharge system Query system which is going to take much of the bandwidth Highly designed User interface with eye catching design (This also results in more bandwidth
requirement)
”
2.0 Project Development Model
2.1 Characteristic of Project“
There are three major consideration involved when speaking about characteristic of the project. These are the factors which determine the success of the project
The operational environment and its characteristics- The system shall be eventually run on either the Internet or the institute’s intranet.
Major system components and the interconnections among these components- The target machine type is a standard PC running one of Windows-9X, NT, 2000, XP, Vista, 7 or Linux or other workstation using Unix.
Interfaces to external systems or procedures- The application shall use a windowing system available with the development system being used. Application data should be held in one or more database files, normal text and Excel files, registry entries and system variables
”
2.2 Project Life Cycle Model
Several stages included in SDLC for this project which described below in bullet forms:
STEP 1: Planning and Requirement Analysis STEP 2: Defining Requirements STEP 3: Designing the product architecture STEP 4: Building or Developing the Product STEP 5: Testing the Product STEP 6: Deployment in the Market and Maintenance
[tutorialspoint.com, 2016]
Considering about all the SDLC methods such as: Waterfall model, Iterative (Agile), spiral, V-model, Big Bang model this project demands Waterfall model.
2.3 Selection of Waterfall Model
There are several factors involved in selecting waterfall model as the SDLC for this scenario. Mainly the requirement and specification is well explained and it’s clear to proceed with the other steps , as there won’t be any return back to requirement gathering step in addition there won’t be any modification as project definition is stable. As a result design of the project is straight forward and easily can satisfy customer needs. Although these factor helps in the project success a lot other important factor is time
management. Comparing and contrasting with other SDLC it’s time savable and can set a target project end time with every phase achievable timing [whatis.com]
3.0 Project Estimates
3.1 Estimation Techniques Applied and Results
Estimation Technique: Function Point (FP)
GUI Simple Average ComplexNumber of User Inputs 10 3 2
Number of User Outputs 7 1 3Number of User Inquiries 9 4Number of Files 1 1 3Number of External Interfaces 2
GUI Functional Point: 227
Database Simple Average ComplexNumber of User Inputs 1 4 2Number of User Outputs 1Number of User Inquiries 13 1Number of Files 3Number of External Interfaces 4
Complexity of Adjustment Table: 28
Database Functional point: 132.54
(Used calculator for FP calculation: Function Point Calculator from CIS 375)
Total of Function point = 132.54 + 227 = 359.54
LOC = FP*30
= 359.54*30 = 10,786.2
Assumption LOC per person month = 200
Average LOC person per month = 53.93
Average FP person per month = 53.93/30 = 1.8
3.2 Estimation Technique: Constructive Cost Model (CoCoMo)
The CoCoMo model was also used to verify the estimate calculated by using the Function Point metric.
This system is assumesd itself to be an Intermediate, Semi-Detached software project.
Effort = a (KLOC) b
Duration = c (Effort) d
Equation values for Effort calculation:
a = 3.0b = 1.12Equation values for Duration calculation:c = 2.5d = 0.35
Estimate for: Constructive Cost Model (CoCoMo)
Effort = 3.0 (10.8) 1.12 = 43.11Duration = 2.5 (43.11) 0.35 = 9.33
Staffing = effort/duration = 4.62
Reconciled Estimate
Effort (in Function Points) Estimate:
Total Function Points: 359.54
Effort (in CoCoMo) Estimate:Effort = 43.11
Time in Person Months Estimate:
Function Point: 1.8CoCoMo: 4.6Average: 3.2
All the values are given have been change to first decimal to make the calculation easy
3.3 Total Cost CalculationTotal cost of the project = Average cost per person * TAS estimated person month
Average cost per person = $ 50.00 per hour
Average cost per month = $50 * 8 * 30
= $ 12,000
Total cost Estimate monthly (Without equipment and other etc): $12,000 * 3.2 = $38,400
Total duration of the project is 9.3 nearly equals to 9 Months,
Total cost estimate staff = $38,400 * 9 = $345,600
Equipment rental = $ 1000 *9*4 = $36,000
Consultation fee = $100/hour
Assuming weekly 5 hours of consultation needed
So, Total consultation fee = $100*5*4*9 = $ 18,000
Overhead = 345,600+36000+18000 = $399,600*30/100
Total overhead = $119,880
COST CATEGORY AMOUNT ($)
Staff 345,600
Consultation fee 18,000
Equipment Rental 36,000
Software purchase 10,000
Overhead 119,880
TOTAL COST ESTIMATION 529,480
4.0 Planning and Scheduling
4.1 Project Resources“
Resources are the factor which is an investment for any project. This project contains three types of resources such as people, hardware, and software.
Required staff:
Web designer
Database administrator Database designer Software programmer Network administrator Windows Help programmer / Tutorial programmer Graphic designer Librarian Document controller
Each of the members have to work as a team in order to complete the project in time and fit into the budget. Staff is the strength and threat for any company, making them as strength is very important to success the project.
Hardware Requirements:
Development
Four IBM PC or compatibles with the following configurations
• Processor – Intel Pentium III with 1000 MHz• SDRAM – Minimum 64MB • Minimum Hard Disk Space- 500GB• Proper network connection with uninterruptable internet
User Client-side
IBM PC or any computers compatibles with the following configurations
• Processor – Intel Pentium II with 333 MHz• SDRAM – Minimum 32MB • Minimum Hard Disk Space- 50GBUser Server-side
IBM PC or compatibles with the following configurations
• Processor – Intel Pentium III with 1000 MHz• SDRAM – Minimum 32MB • Minimum Hard Disk Space- 20 GB
Software Requirements:
• Windows 98• Windows NT Workstation• Windows NT Server
• Visual Basic 6.0 (three user licenses)• Microsoft Access 97 and 2000• Microsoft Word 97 and 2000
”
4.2 Task List“
1.0 Scope1.1 Determine Project scope1.2 Secure project sponsorship1.3 Define preliminary resources1.4 Secure core resources1.5 Scope completion
2.0 Analysis requirement2.1 Conduct need analysis2.2 Draft preliminary hardware, software requirement2.3 Develop preliminary budget2.4 Review budget and compare with specification2.5 Feedback on requirement2.6 Develop delivery timeline2.7 Obtain approvals to proceed2.8 Analysis completion
3.0 Database design3.1 Requirement analysis3.2 Conceptual database design (ER-Diagram)
3.2.1 Identifying fields, tables3.2.2 Determining the relationship between tables3.2.3 Adding data and creating other database feature3.2.4 Refining the design
3.3 Logical database design3.4 Physical database design3.5 Finalizing the design3.6 Develop the database using appropriate software3.7 Testing the design
4.0 Web Development4.1 Review functional specification4.2 Identify modular/tiered design parameters4.3 Assign development staff4.4 Develop code4.5 Developer testing4.6 Development complete
5.0 Testing5.1 Test plan creation5.2 Component test5.3 Module test5.4 System integration test5.5 Product validation test5.6 Technical construction file5.7 Review of design and test plans “
6.0 Documentation6.1 Develop help specification6.2 Develop help system6.3 Review help documentation6.4 Develop user manuals6.5 Review all user documentation6.6 Documentation complete
”
4.3 Task Network
TEACHING ALLOCATION SYSTEM (TAS)Scope
Database design
Web Development
Testing Documentation
Analysis Requirement
4.4 Work Break down Structure (WBS)
ScopeDatabase
DesignWeb
DevelopmentTesting
Determine Project Scope
Secure Project Sponsorship
Secure core resources
Test plan creation
Component Test
Module Test
System Integration
Test
Product validation
Test
Technical construction
File
Review of Design and Test
plans
Requirement Analysis
Conceptual
database designIdentifying fields, tables
Determine the relationship between tables
Adding data and creating other database feature
Refine the design
Logical database
design
Review functional specification
Define modular design parameters
Assign development staff
Develop code
Physical database
design
Finalizing the design
Developer testing
Development guide
Teaching Allocation System (TAS)
Define Preliminary Resources
Scope completion
Analysis Requirement
Documentation
Develop help specification
Develop help system
Review help documentation
Develop user manuals
Review all user documentation
Documentation complete
1.11.2
Analysis Requirement
Conduct need analysis design
Draft preliminary hardware, software requirement
Develop preliminary budget
Obtain approvals to proceed
Analysis completion
Review budget and compare with specification
Develop delivery timeline
Feedback on requirement
4.5 Gannt chart
4.5.1 Snapshot of Gannt chart figures “
The time frame needed for this project the sum of the days allocated in gannt chart which is almost nearly equal to days calculated in previous section (9.3 months). According to gannt chart it needed 270 days to complete the project. This is the minimum target to achieve the successful project completion. Milestones are created in order to complete each task one by one and each end report will be generated.
4.5.2 Resource allocation
Assumed as developers and designers are same role in this project.
As per the gannt chart results there is no over allocation needed to this project as it’s perfectly planned and assumed software will be easily gettable in point of project’ view and needs.
5.0Risk Analysis
5.1 Introduction
Keeping all things error free and risk free is hard when it comes to system. Innovating and presenting a system without any defect is almost impossible. Every project leader and owner and sponsor must ensure the adequate and timely risk identification performed in regular gap throughout the project. Whenever the risk is identified a perfectly plan has to be executed to counter effect the threat or the risk. Most appropriate way to do is to assign certain set of people to do risk analysis, identification and solution.
5.2 Risk identification and analysis“
Risk identification is the major thing when comes to the point of risk. There are various methods used in industry and for this project it will be applied so, Methods are listed below
Past project data and the results will be a helpful to counter any risk and identify the risk Technical expertise and experience of the employee working in the project is one of the
key factor in identification Face to face communication and questionnaire will be helpful to identify risk during the
project
Risk can be identified under several categories for example scope, or it can be social factor it depends upon the risk. Risk which is identified in this project as follows:
Scope
While discussing requirement due to ineffective communication and negotiation between stakeholders and employee will lead into high risk of project failure
Stakeholders
Inability to motivate the project team Due to high regulation from government authorities Lack of contribution and low level of dedication in work must lead into a project failure
Social Factor
Entering and designing, implementing a new system and method which is not available in the market with an inexperienced team with a new way of approach will creates a risk in the working environment
Using different switching process inside the organization also within the project team
Economic factor
Economic crisis and the equipment and labor cost can rise up when project progress this leads into budget goes further high which will push the project to be delayed
Inflation rate can cause loss of money
Market factor
Inability to build a trust in the market and among stakeholders Difficulty in establishing an identity for the device Affection of Future due to other competent companies’ failure
Legal factor
Regulation for the product in sales or using and proprietary rights
Technical factor
Technical factor can be further divided into two categories, it’s described below:
User
User’s resistance to change Conflicts between users Users with negative attitudes toward the project Users not committed to the project Lack of cooperation from users
Requirement
Continually changing requirements System requirement not adequately identified Unclear system requirements Incorrect system requirements
[Arnuphaptrairong,2011]
”
5.3 Probability-impact of risk“
NO RISK DESCRIPTION
RISK CATEGORY PROBABILITY IMPACT
1 Regulations for online purchase and payment
Legal factor MEDIUM 2
2 Entering with the new business equipment and method with inexperienced team
Social factor MEDIUM 5
3 Using different process within the organization
Social factor MEDIUM 4
4 Ineffective communication and negotiation- less time effective
Scope MEDIUM 4
5 Inability to motivate project team
Stakeholders MEDIUM 3
6 Regulation of government agencies
Stakeholders LOW 4
7 Lack of contribution of functional managers
Stakeholders LOW 3
8 Economic crisis make cost to
Economic factor MEDIUM 2
rise up9 Inflation rate
might cause loss of money
Economic factor MEDIUM 2
10 Inability to develop and trust in market
Market LOW 5
11 Difficulty in establishing an identity for the device
Market MEDIUM 4
12 Affection of future due to other competent companies’ failure
Market MEDIUM 4
13 User’s resistance to change
Technical LOW 3
14 Conflicts between users
Technical LOW 2
15 Users with negative attitudes toward the project
Technical MEDIUM 3
16 Users not committed to the project
Technical MEDIUM 4
17 Lack of cooperation from users
Technical LOW 2
18 Continually changing requirements
Technical MEDIUM 2
19 System requirement not adequately identified
Technical HIGH 5
20 Unclear system requirements
Technical HIGH 4
21 Incorrect system requirements
Technical HIGH 5
”
5 10 2 19,21
4 6 3,4,11,12,16 20
IMPACT 3 7,13 5,15
2 14,17 1,8,9,18
1
LOW MEDIUM HIGH
PROBABILITY
Risk impact- probability table
5.4 RMMM plan“
Risk log table is presented above and followed by probability impact grid (PIG) which was used for the purpose of risk response planning. There are four possibilities of how to respond to the risks defined in the risk log has been provided below; avoid, mitigate, accept or transfer. It is recommended that risks within yellow and red zones are assigned to the project team members. Therefore all of the risks identified in the risk management process will be assigned to specific person in the project team to be reviewed and mitigated.
After the third part of the process (responding to the project risks), project risks reviewing needs to be done throughout the project life cycle so that mitigation as well as other responses to them can be up to date.
RISK DESCRIPTION RISK CATEGOR
Y
PROBABILITY
IMPACT
RESPONSE NEW PROBABIL
ITY
NEW IMPAC
TRegulations for online purchase and payment
Legal factor MEDIUM 2 Accept MEDIUM 2
Entering with the new business equipment and method with inexperienced team
Social factor MEDIUM 5 Due diligence exercise LOW 3
Using different process within the organization
Social factor MEDIUM 4 Avoid MEDIUM 4
Ineffective communication and negotiation- less time effective
Scope MEDIUM 4 Project Manager negotiation skills improved
LOW 4
Inability to motivate project team
Stakeholders MEDIUM 3 Communication plan LOW 2
Regulation of government agencies
Stakeholders LOW 4 Accept MEDIUM 4
Lack of contribution of functional managers
Stakeholders LOW 3 Communication plan LOW 2
Economic crisis make cost to rise up
Economic factor
MEDIUM 2 Accept MEDIUM 2
Inflation rate might cause loss of money
Economic factor
MEDIUM 2 Accept MEDIUM 2
Inability to develop and trust in market
Market LOW 5 Memorandum of understanding MEDIUM 4
Difficulty in establishing an identity for the device
Market MEDIUM 4 Memorandum of understanding MEDIUM 3
Affection of future due to other competent companies’ failure
Market MEDIUM 4 Liability Limited MEDIUM 3
User’s resistance to change Technical LOW 3 Communication plan and make them understand should accept the risk
LOW 1
Conflicts between users Technical LOW 2 Communication plan and make them understand should accept the risk
LOW 1
Users with negative attitudes toward the project
Technical MEDIUM 3 Communication plan and make them understand should accept the risk
LOW 2
Users not committed to the project
Technical MEDIUM 4 Communication plan and make them understand should accept the risk
LOW 3
Lack of cooperation from users
Technical LOW 2 Communication plan and make them understand should accept the risk
LOW 1
Continually changing requirements
Technical MEDIUM 2 Clearly understand the basic requirement and react to that, proper weekly meetings
will reduce the risk
LOW 2
System requirement not adequately identified
Technical HIGH 5 Clearly understand the basic requirement and react to that, proper weekly meetings
will reduce the risk
MEDIUM 4
Unclear system requirements
Technical HIGH 4 Clearly understand the basic requirement and react to that, proper weekly meetings
will reduce the risk
MEDIUM 3
Incorrect system requirements
Technical HIGH 5 Clearly understand the basic requirement and react to that, proper weekly meetings
will reduce the risk
MEDIUM 3
”
6.0Appendix
6.1 14 point questionnaire
Complexity of Adjustment Table (example of the 14 questionnaire table)
6.2
CoCoMo Value chart
6.3 Probability impact grid of tasks
6.4 Gannt chart with resource
IMPACT RATING
HIGH - 5
MODERATE - 4
MEDIUM - 3
MINOR - 2
LOW - 1
Reference
"Defining The System Context | Flamelab.De". flamelab.de. N.p., 2009. Web. 12 Apr. 2016. Mochal, Tom. "Define Project Scope To Include Deliverables, Boundaries, And Requirements -
Techrepublic". TechRepublic. N.p., 2007. Web. 13 Apr. 2016. "SDLC - Quick Guide". www.tutorialspoint.com. N.p., 2016. Web. 13 Apr. 2016. "What Is Waterfall Model? - Definition From Whatis.Com". SearchSoftwareQuality. Web. 12
Mar. 2016. Arnuphaptrairong, Tharwon. "Top Ten Lists Of Software Project Risks : Evidence From The
Literature Survey". N.p., 2011. Web. 17 Apr. 2016.