Download
student academic plan by team netinfotech n.
Skip this Video
Loading SlideShow in 5 Seconds..
Student academic plan by team netinfotech PowerPoint Presentation
Download Presentation
Student academic plan by team netinfotech

Student academic plan by team netinfotech

123 Vues Download Presentation
Télécharger la présentation

Student academic plan by team netinfotech

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Student academic planbyteam netinfotech April 30, 2013

  2. Introduction to the Team

  3. Organizational charts

  4. Roles and Responsibilities

  5. Responsibilities • Project manager • Mohammad Nuruzzaman • To 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.

  6. Responsibilities • Risk/QA Manager • Karan 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.

  7. Responsibilities • Technical Head • Paola Morales • Database and programming Decisions • Code inspections on a regular basis • To lead the design and impletion phase

  8. Responsibilities • Design Architect • Manish • Produce a design of the software based on SRS • Supervise documentation of SADD and SDD • To ensure the design is through and easily implemented by the programmers.

  9. Responsibilities • Dinesh • Web developer • To deign the interface of the system • Web page is up to date

  10. Introduction to the client

  11. Introduction to the Project • Web based database system to manage academic plans for new and continuing students • Budget: $10,000 • Time: 3 months

  12. 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

  13. Project Scope • Project name- Student Academic Plan System • Project Justification • Product Characteristics and Requirements • Project/Product Deliverables • Risk Management • Success Criteria • Assumptions

  14. 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..

  15. Project Scope Product 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.

  16. Project Scope Risk • Absence of team members. • Lack of communication. • Conflict with client. • System failure.

  17. Project Scope Project 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.

  18. Project Scope Assumptions: • 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.

  19. Project Deliverables • SDD • Test Plan • Quality Assurance Plan • Risk Management Plan • Source and Object code • SPMP • WBS • Status Reports • Milestone Reports • SRS • SADD

  20. Development Methodology Clear Specification…. Waterfall methodology • Requirements phase • Design phase • Implementation • Testing • Maintenance

  21. WBS

  22. WBS-2

  23. Gantt Chart

  24. Gantt Chart

  25. Network Diagram

  26. Network Diagram 2

  27. Network Diagram 3

  28. Network Diagram 4

  29. Network Diagram 5

  30. Requirements and Architecture Context Diagram

  31. Requirements and Architecture E-R Diagram 1

  32. Requirements and Architecture E-R Diagram 2

  33. Requirements and Architecture E-R Diagram 3

  34. Requirements and Architecture Data Dictionary

  35. Requirements and Architecture Use case Model 1

  36. Requirements and Architecture Use Case Model 2

  37. Requirements and Architecture Activity Diagram 1

  38. Requirements and architecture Activity Diagram 2

  39. Requirements and Architecture Data Flow Diagram

  40. Requirements and Architecture LOGIN Student Academic Plan system Course Coordinator Administrator

  41. Tools and Technologies • PHP • MYSQL • Workbench • HTML • Dreamweaver • Enterprise Architect

  42. Quality Control • QA Manager • Product has complete functionality • Product meets client requirements

  43. Quality Control • Procedures • Internal Reviews • External Reviews

  44. 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.

  45. Quality Control-Coding All codes will be clearly commented

  46. Quality Control-Approval • All core functional requirements are implemented. • All non-functional requirements are satisfied. • User documentation has been provided. • Test Plan

  47. Quality Control-Test Plan • Functional Testing : Black Box • Code Testing: White Box • Non Functional Requirements: Performance or reliability • Simulation / Load Test

  48. References • Heldman, 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

  49. Any Questions ? Thanks for attending the Presentation Netinfotech Team