MIS 430 1 Exam Practice Questions and Answers

MIS 430 1 Exam Practice Questions and Answers feature vs design - Ans:-feature: what the system needs to do Design: how the system delivers those features Why are software projects difficult/risky? - Ans:-•Poor software construction-Not running as designed •Poor software requirements -Wrong features: what the system needs to do -Wrong design: how the system delivers those features, Data, Logic, UI Construction - Ans:--Traditional approach -Programming new features (e.g. Java, C#, or Python) Configuration - Ans:--Increasingly important alternative ©GRACEAMELIA 2024/2025 ACADEMIC YEAR. ALL RIGHTS RESERVED FIRST PUBLISH OCTOBER 2024 Page 2/11 -Selecting and configuring third-party software -COTS (commercial-off-the-shelf) software Current vs Future state - Ans:-Future state: Identifying new user stories from new functionality across the automation boundary Build formula - Ans:-Build = Future State - Current State + Re-engineering* *problematic current capabilities -legacy code, poor design, etc. -Inadequate infrastructure Why is cyber security an increasing concern? - Ans:-Driven by: •Increasing amounts of sensitive, confidential data •Systems accessible via the Internet •Risk of hackers: -External -Internal ©GRACEAMELIA 2024/2025 ACADEMIC YEAR. ALL RIGHTS RESERVED FIRST PUBLISH OCTOBER 2024 Page 3/11 plan driven approach - Ans:-Big Requirements Up-Front (BRUF) •High Clarity: We can clearly understand what we need and describe the design •High Stability: What we need won't change significantly during construction •High Interdependence: We can't change the foundation late in the project without rework and increasing costs Plan-driven requirements - Ans:-Comprehensive Requirements: BRUF (Big Requirements Up Front) and BDUF (Big Designs Up Front):Fully detailed features and designs Fixed Scope: No scope changes once project approved Ongoing requirements: None Single, long-phase of construction precludes on-going requirements Non-Iterative construction: ·Single-phase ©GRACEAMELIA 2024/2025 ACADEMIC YEAR. ALL RIGHTS RESERVED FIRST PUBLISH OCTOBER 2024 Page 4/11 ·Long-duration ·Customer testing and feedback on delivery Agile approach - Ans:-•Low Clarity: We have only a rough idea of what we need, with details depending on on-going conversations and feedback •Low Stability: What we need will change significantly during construction •Low Interdependence: Because features are independent, we can build them in any order. So we welcome late updates to requirements, because they don't cost much an