Business Case Analysis Assumptions Users want a way to analyze the quality of the software they have developed, managed, or invested in. Users will make business decisions based on the findings revealed by the software quality analysis. Users will access the system using Chrome on Desktop devices. Users will create an account using their email address. Stakeholders Initiatives Value Propositions Beneficiaries are Developer - CSCI 577 Team Maintainer - Pooyan Client - Pooyan Admin - Pooyan Users - Researcher, Project Manager, Contributors (Navy, NASA, students) Developers: Develop system Maintainer: Maintain the system Client: Properly host system using HTTPS, Advertise the system Admin: Manage user permission Users: Present project for analysis, hoping to examine software quality across various metrics. Users able to analyze projects using various software quality metrics. Users able to evaluate development team member contributions to software quality Opportunity to fix major flaws identified by software quality metrics. Grow system’s customer base. Users can better understand the value of their investment. System security will be consistent with industry standards. Client Users - Researchers, Project Manager, Contributors
Process Feasibility Decision Criteria Rating Scale: 0:Very Low; 1:Low; 2:Medium; 3:High; 4:Very High Importance Rating Scale: 1:Low; 2:Medium; 3:High Table 8: Rationales for Selecting Architected Agile Model Criteria Importance Project Status Rationales 30 % of NDI/NCS features 3 4 Using ReactJS, ReactBootstrap, PrimeReact Single NDI/NCS 1 0 There is no a NDI/NCS that can support all project expectation. Unique/ inflexible business process 2 3 The business process is not unique and able to negotiate wit h client. Need control over upgrade / maintenance 3 1 Project should be easy to add more metrics. Rapid deployment 2 2 The deployment deadline is Apr, 20 2018. I Critical on compatibility 3 3 This project must compatibility with chrome browser. Internet connection independence 1 0 Need internet connection to connect with backend server. Need high level of services / performance 3 2 20 users can work on the system simultaneously. Need high security 3 4 User and password requires for user authentication. Asynchronous communication 1 1 All communication are synchronous. Be accessed from anywhere 1 2 Internet is need to access web application. Critical on mass schedule constraints 1 0 No mass schedule.
Risk Assessment Table 9: Risk Assessment Risks Risk Exposure Risk Mitigations Potential Magnitude Probability Loss Risk Exposure Vague definition of statistical analysis view. 7 9 63 implement prototype for layout and data visualization to narrow down implementation options Ambiguity in definition of Access Control for users of the application 7 8 56 implement use case diagram and activity diagram for access control flow and discuss with client Client doesn’t have final idea on user interfaces 7 8 56 Team design and implement wireframe prototype and discuss with client. Not consulting end users. 6 8 48 Should gather feedback and interact with eventual to establish initial requirements. Collaboration may be difficult, and siloing may occur within the team. 4 9 36 Establish a plan for collaboration, so that very large deliverables are not assigned to only an individual. D3 might be unwieldy in React framework 4 7 28 Create a basic view as a dummy prototype Programmatic testing might go unexplored 5 5 25 Consider the risks of not including code-based testing practices. Research available options and possibly implement tests, depending on risk factors.