Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Software Engineering Capstone SWE 481 Group 4 Group Project Phase 5

1,274 views

Published on

  • Be the first to comment

  • Be the first to like this

Software Engineering Capstone SWE 481 Group 4 Group Project Phase 5

  1. 1. Software Engineering Capstone 1 SWE 481 Capstone Mobile Banking Software Development Plan Group 4 Created and Edited by: Jim Richardson Approved by: Robert Perry & Alex Wiebold December 22, 2014 Page 1
  2. 2. Project Outline  Capstone Bank decides to modernize their financial institution to appear more modern and competitive.  Capstone Bank explores options.  Capstone Bank determines they need to add a new service.  Capstone Bank decides upon the new service…  Mobile Banking! Page 2
  3. 3. Project Outline: Mobile Banking  Capstone Bank’s new service: Capstone Bank Mobile Banking.  Capstone Mobile Banking will include the following major features:  Login  View Balances  Transfer Funds  Make Photographed Deposits  Link Accounts  View Financial Statements • Major issues to consider Page 3
  4. 4. Development Methodology  Scrum  What is Scrum?  Sprints  Two to four week iterations  Major Roles of Scrum  Product Owner  Scrum Master  Scrum Project Team  How does Scrum work?  Major Activities  Sprints  Sprint planning meetings  Daily Scrum meetings  Sprint Review meetings  Sprint Retrospective meetings Page 4(“Scrum Methodology”, 2014; Rouse, 2014; “Scrum Methodology”, n.d.; “What is Scrum”, n.d.)
  5. 5. Scrum Software Development Model (“Why should we”, 2014) Page 5
  6. 6. Scrum Software Development Model (“Why should we”, 2014; “Features of Scrum”, 2014; Uhlig, n.d.)  Why should we choose Scrum?  Provides a working model earlier than traditional Software Development Models  Frequent Requirement Changes is less impactful  Self- Organization and employee empowerment  Open and frequent Communication  Opportunities for clear definitions  Promotes Creativity, Collaboration, and Collaboration  Improved processes  Capitalizes upon feedback  Iterative and Incremental working models  Backlogs work items for better realization of work schedules and required work Page 6
  7. 7. Requirements  Requirements Elicitation  How will we elicit the requirements? Stakeholder Meetings Informal Interviews Requirements Surveys  What do we do with the elicited requirements? Brainstorm Storyboard Backlog Begin the processes of designing and developing the product Page 7
  8. 8. Requirements  Approved Requirements  Functional Requirements  Login  View Balances  Link Accounts  Photograph Deposits  Transfer Funds  View Financial Statements  Non-Functional Requirements  Secure Connection and Encrypted Data Transfers – 128-bit encryption and decryption on the fly  Prevention of Simultaneous Logins – no more than one login instance at a time  Application Loading – 7 second load time  Refresh Rate – automatically refreshes account balances every 60 seconds  System Lock Out – locks the system after 5 failed attempts to authenticate  System Time Out - logs the user out after 10 minutes of inactivity Page 8
  9. 9. Design: Component Diagram Page 9
  10. 10. Design: UML Use Case Diagram Page 10
  11. 11. Design: UML Use Case Diagram Exploded View Page 11
  12. 12. Design: UML Class Diagram Page 12
  13. 13. Design: User Interface Prototype Page 13
  14. 14. Development and Testing  Development  Milestone identification and tracking using Computer Aided Software Engineering (CASE) Tools: Microsoft Project  Milestone identification  Finished product becomes a milestone  Daily Scrum Meetings will produce mini-milestones  Tracking  Monthly Stakeholder Meetings will disclose the milestones  Work Breakdown Schedule (WBS)  Gantt Chart  Network Diagram  Testing  Testing will occur within each sprint  Testing conventions:  Black Box Testing – Unit Testing  Black Box Testing – Integrating Testing  White Box Testing – Usability Testing  White Boxy Testing – Automated Regression Testing  Black Box Testing – System Testing Page 14(Scrumstudy, n.d.)
  15. 15. Development and Testing Page 15(Scrumstudy, n.d.)
  16. 16. Project Schedule  CASE Tool: Microsoft Project  Provides better organization  Lists the project schedule  Lists the milestones  Lists detailed tasks for each milestone  Provides a view of the Critical Path  Project Schedule  Best case estimates  Incorporated “Float Time”  Tracking  Story points will be moved to the Completed Work section on the project storyboard  MS Project will be updated with a color-coded scheme and the Gantt Chart will illustrate percent complete Page 16(“Leads, Lags and Floats”, 2014)
  17. 17. Project Schedule Page 17(Csaba, 2013; “Release Burndown Chart:, 2014)
  18. 18. Risk Analysis  What is a project risk?  An event that could potentially hinder or negatively affect the project in such a manner that the project fails to achieve its objectives  What do we do about project risks so that the project is successful?  Project Risk Management Plan  Identify Risks  Risk Identification Matrix  Evaluate Risks  Impact and Probability Scale  Develop Risk Response Plan  Avoid, Mitigate, Accept  Review Project Risks Frequently Page 18(“What is a project risk”, n.d.; PMI, 2009, p.4; Yegi, 2014)
  19. 19. Risk Analysis Page 19
  20. 20. Risk Analysis Page 20
  21. 21. References  Csaba, P. (2013, January 10). SCRUM: The story of an agile team. Retrieved from Envato Pty Ltd. website: http://code.tutsplus.com/tutorials/scrum-the-story-of-an-agile-team--net-29025  Features of Scrum. (2014). Retrieved from The Braintrust Consulting Group website: http://braintrustgroup.com/scrum/features-of-scrum/  Lead, Lags and Floats. (2014). Retrieved from Tutorialspoint website: http://www.tutorials point.com/management_concepts/leads_lags_floats.htm  PMI. (2009). Practice standard for project risk management (p. 9). Newtown Square, PA: PMI Publications.  Release Burndown Chart. Topics in Scrum (2014). Retrieved from Mountain Goat Software website: http://www.mountaingoatsoftware.com/agile/scrum/release-burndown  Rouse, M. (2014). Agile Manifesto. Retrieved from Tech Target website: http://searchcio. techtarget.com/definition/Agile-Manifesto  Rouse, M. (2014). Scrum. Retrieved from Tech Target website: http://searchsoftware quality.techtarget.com/definition/Scrum  Scrum Methodology. (2014). Retrieved from Scrum Methodology website: http://scrum methodology.com/  Scrumstudy.com. (n.d.). Scrum Phases and Processes. Retrieved from Scrumstudy.com: http://www.scrumstudy.com/scrum-phases-processes.asp  Uhlig, D. K. (n.d.). Advantages and Disadvantages of the Scrum Project Management Methodology. Retrieved from Chron.com: http://smallbusiness.chron.com/advantages-disadvantages-scrum-project- management-methodology-36099.html  What is a project risk? (n.d.). Retrieved from Project Future 2 website: http://www.projectfuture.net/uk/projectfuture-software/frequently-asked-questions/what-is-a-projectrisk  Why should we choose SCRUM for our project. (c. 2014). Retrieved from http://sandervanpeer.wordpress.com/2012/01/05/why-should-we-choose-scrum-for-our-projects/ on November 24th, 2014.  Yegi, S. (2014). Risk and Issue Management in the Scrum Process. Retrieved from Scrum Alliance website: https://www.scrumalliance.org/community/articles/2014/april/risk-and-issue-management-in-scrum- process Page 21

×