student academic plan by team netinfotech
DESCRIPTION
Student academic plan by team netinfotech. April 30, 2013. Introduction to the Team. Organizational charts. Roles and Responsibilities. Responsibilities. Project manager Mohammad Nuruzzaman To distribute tasks amongst group members and record tasks allocated at the regular meetings. - PowerPoint PPT PresentationTRANSCRIPT
STUDENT ACADEMIC PLAN
BYTEAM NETINFOTECH
April 30, 2013
Introduction to the TeamName Role Phone E-mail
Mohammad Nuruzzaman Project Manager 61405062921 [email protected]
Karan Jalan Risk/QA Manager 61452233047 [email protected]
Paola Morales Technical Head 61431193001 [email protected]
Manish Design Architect 61432073811 [email protected]
Dinesh Web Developer 61451450778 [email protected]
Organizational charts
Mohammad Nuruzzaman
Project Manager
Karan JalanRisk/QA Manager
Paola MoralesTechnical
Head/Developer
ManishDesign
ArchitectDinesh
Web developer
Roles and Responsibilities
ResponsibilitiesProject managerMohammad NuruzzamanTo distribute tasks amongst group members and record tasks allocated at the regular meetings.
To provide regular feedback to supervisors and team members.
To be available for team members to see when there is a problem within the group. To ensure that the project keeps to the schedule.
ResponsibilitiesRisk/QA ManagerKaran Jalan To alert team members when a risk is identified
To suggest possible solutions for problems arising within the team
Suggest a way to prevent the same type of risk from occurring.
To identify, assess, manage and document the risks that may occur during the course of the project.
ResponsibilitiesTechnical HeadPaola Morales Database and programming DecisionsCode inspections on a regular basisTo lead the design and impletion phase
ResponsibilitiesDesign ArchitectManish Produce a design of the software based on SRSSupervise documentation of SADD and SDDTo ensure the design is through and easily implemented by the programmers.
ResponsibilitiesDineshWeb developer
To deign the interface of the systemWeb page is up to date
Introduction to the clientRole Name Phone E-mail
Sponsor Siddarth 61405062921 [email protected]
Client Nadil 61452233047 [email protected]
Project Supervisor KT Lau 61431193001 [email protected]
Introduction to the Project Web based database system to manage
academic plans for new and continuing students
Budget: $10,000 Time: 3 months
Client requirements Currently IIBIT uses Microsoft Excel to
manage academic plans Web based student study plan system Should retrieve number of students enrolled
per course Should retrieve courses taken by a student in
current, past and future semester Might retrieve grades of students
Project Scope Project name- Student Academic Plan System Project Justification Product Characteristics and Requirements Project/Product Deliverables Risk Management Success Criteria Assumptions
Project Scope Project Title: Student Academic Plan System. Project Justification: To establish a administration database system for IIBIT to
choose courses for students. The project includes web-based application, login system, database, gantt chart, network diagram, schedule, risk management plan, work breakdown structure, milestone reports, project scope statement and it also includes weekly team meeting minutes, weekly review meetings, change requests and lesson learned, kick-off meetings minutes..
Project ScopeProduct Characteristics and Requirements: Login functionality is required. The System should be user friendly. Online system should be attractive and time efficient
for the users. Course coordinators can choose courses for students
for current and future semesters. System should be secured enough to store personal
information about students.
Project Scope
Risk Absence of team members. Lack of communication. Conflict with client. System failure.
Project ScopeProject Success Criteria: Come up with a weekly report. Proper communication with team members and work
as group. Kick off meetings. To understand your part and work on that as a
responsibility and we ready to help each other. Always have a contingency plan for every step. Try to avoid absentism which leads to the failure.
Project ScopeAssumptions: We assume that the client (Nadil) will be the only user of the
system being developed. We assume that we have student and course database for
IIBIT. We assume that the client have a user ID and password to
login into the system We assume that while choosing courses prerequisites or
student background will not be verified. We assumed that system can work all webbrowsers i.e.
iexplorer, opera, chrome, firefox, safari so on.
Project Deliverables
SPMP WBS Status Reports Milestone Reports SRS SADD
SDD Test Plan Quality Assurance Plan Risk Management Plan Source and Object
code
Development MethodologyClear Specification….Waterfall methodology Requirements phase Design phase Implementation Testing Maintenance
WBS
WBS-2
Gantt Chart
Gantt Chart
Network Diagram
Network Diagram 2
Network Diagram 3
Network Diagram 4
Network Diagram 5
Requirements and Architecture
Context Diagram
Requirements and Architecture
E-R Diagram 1
Requirements and Architecture
E-R Diagram 2
Requirements and Architecture
E-R Diagram 3
Requirements and Architecture
Data Dictionary
Requirements and Architecture
Use case Model 1
Requirements and Architecture
Use Case Model 2
Requirements and Architecture
Activity Diagram 1
Requirements and architecture
Activity Diagram 2
Requirements and Architecture
Data Flow Diagram
Requirements and Architecture
Student Academic Plan system Course
CoordinatorAdministrator
LOGIN
Tools and Technologies
PHPMYSQLWorkbenchHTMLDreamweaverEnterprise Architect
Quality Control
QA Manager Product has complete functionality Product meets client requirements
Quality Control
ProceduresInternal Reviews
External Reviews
Quality Control-Internal Review
1. The team or the PM requests an Internal Review.2. A team member conducts the review.3. The team will review the document within a time frame set by the PM.4. The PM will print a hard copy and make
suggestions on the hard copy.5. The PM will contact the client and discuss any quality issues. If the client is not satisfied, the team will be consulted at the next meeting.
Quality Control-Coding1. All codes will be clearly
commented
Quality Control-ApprovalAll core functional
requirements are implemented.All non-functional requirements
are satisfied.User documentation has been
provided.Test Plan
Quality Control-Test Plan Functional Testing : Black Box
Code Testing: White Box
Non Functional Requirements: Performance or reliability
Simulation / Load Test
ReferencesHeldman, K. (2006). Project Management Professional Study Guide. Hoboken: John Wiley & Sons, Inc.International journal of project management(2006). Retrieved 24th March 2013,http://www.sciencedirect.com/science/article/pii/S0263786306001438
Kerzner, H. (2010). Organizing and staffing the project office and team. Project Management:Approach to Planning, Scheduling, and Controlling (pp. 141-144), Wiley.
Milestone report (2007).Retrieved 2nd April 2013, from
http://www.dairyaustralia.com.au/Industry-overview/Research-and-development/Research- Funding/Reporting-Requirements/Milestone-Reports.aspx
Project Risk management (2012). Retrieved 4th April 2013, from http://www.projectperfect.com.au/info_risk_mgmt.php
Project scope management (2010).Retrieved 6th April 2013, from http://www.fastprojectplans.com/scope-management-plan-template.html
Larson, E. & Gray, C. (2011) Project Management: The Managerial Process (5th Ed) Chapter 2, 3.Lewis R. Ireland (2006) Project Management. McGraw-Hill Professional, 2006. p.110.Joseph Phillips (2003). PMP Project Management Professional Study Guide. McGraw-Hill Professional, 2003. p.354.PMI (2010). A Guide to the Project Management Body of Knowledge p.27
Any Questions ?Thanks for attending the
Presentation
Netinfotech Team