MIS 5203 Week 1 -1 Presentation - Temple MIS

1y ago
13 Views
2 Downloads
1,014.53 KB
27 Pages
Last View : 1d ago
Last Download : 2m ago
Upload by : Albert Barnett
Transcription

MIS 5203 Systems & Infrastructure Lifecycle Management 1 Week 4 February 04, 2016

Study Objectives Traditional SDLC Waterfall Method and its Variants Requirement Phase Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 2

Systems Development Life-Cycle (SDLC) What are traditional SDLC Phases? A. B. C. D. E. F. G. H. I. Requirements Feasibility Risk Management Design Development Project Planning Performance Testing Implementation Post Implementation Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 3

CISA SDLC Phases and Relationship Phase 1 – Feasibility Build Phase 2– Requirements Buy Phase 3 A– Design Phase 3B– Selection Phase 4A – Development Phase 4B– Configuration Phase 5 – Implementation Reviews at the end of each phase acts as “stage gate” Phase 6 – Post Implementation Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 4

Traditional SDLC Phases Phase 1 Feasibility Phase 2 Requirements Phase 3 Design/Selection Phase 4 Development/ Configuration Phase 5 Implementation Phase 6 Post Implementation Phase Phase Name Key Items 1 Feasibility - Feasibility, Business Case, ROI 2 Requirements - Business Requirements, Systems Requirements Vendor Requirements 3A OR 3B Design - Systems Architecture: overall system High Level Design: overall system Detailed Design: module, interface, sub-systems, service, database, UI etc. Selection of Vendor and Vendor supplied system - Coding Testing: unit, integration, systems, performance Configuration of the Vendor supplied system Selection 4A OR 4B Development 5. Implementation - Data Conversion, Change Management, Implementation Final UAT Incident, Outage, and Availability Management 6. Post Implementation - Lesson Learned Evaluation of Benefits vs. Business Case Configuration Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 5

Water-Fall SDLC Model Barry Boehm’s water-fall model Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 6

Waterfall Model One of the common and traditional SDLC methodology Barry Boehm’s modified SDLC model in 1970s Feedback loop allows for validation between successive phases Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 7

Waterfall Model When will you use? Come up with Examples (5 minutes) Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 8

Waterfall Model - Pros and Cons Structured Works well when requirements are well defined Better for relatively larger projects Better if there is time in hand Too much documentation Making changes becomes difficult during SDLC Speed to market – not quick Delay in implementation Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 9

Verification and Validation Model (V Model) Adapted from “CISA Review Manual” ISACA, Exhibit 3.8” V-Model is a variant of water-fall model Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 10

Spiral SDLC Model Spiral Model is a variant of water-fall model Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 11

Spiral SDLC Model It’s iterative Each iteration goes through mini-waterfall Gives Business Team time to refine and prioritize requirements Helps assess Business Value before committing to entire project Helps course correct More common than traditional waterfall SDLC Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 12

Question What’s the main reason of the reviews at the end of each phase in the SDLC? A. Funding Approval to continue development B. Approval by management to proceed to the next phase or possibly kill the project (stage gate) C. Design and Code Familiarity D. Internal Auditor compliance Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 13

Requirement Phase Phase 1 Feasibility Phase 2 Requirements Phase 3 Design/Selection Why is Requirement Definition Important? Phase 4 Development/ Configuration Phase 5 Implementation Phase 6 Post Implementation A. Helps Define Business Needs B. Helps come up with systems requirements C. Makes Business “wish list” to more concrete definition of the ask D. Provides foundation to the rest of the SDLC phases E. All of the above Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 14

Business/User Requirements Defines functional needs of the Business and how systems should solve it Includes operational, quality, and performance needs as well Many times not written concisely Describe from users’ perspective what they want Could have “must-have” as well as “nice to have” requirements that need to be further prioritized Example: “1. Provide ability to collect user name and address field in a web UI” Generally written by the Users or Business Team Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 15

Systems Requirements Defines functional needs of the Business and how systems should solve it, from systems perspective Includes operational, quality, and performance, interface, reporting, troubleshooting requirements as well Written concisely Describe from users’ perspective what they want, as well from systems perspective how would the systems handle them Would have “must-have” as well as “nice to have” requirements that are prioritized Traceability is often included Specificity is the goal rather than generality Tools such “Use Case” is used to determine systems behavior Written by the IT Team in collaboration with Business and Design Teams Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 16

Business vs. Systems Requirements Example 1. Provide ability to collect user name and address field in a web UI. The customer should be able to submit name and address data before proceeding to the ordering page. 1.1 Provide ability to enter person’s first name and last name in separate input fields 1.2 Provide ability to enter address, which would have Street number, Street name, city, and zip code in separate input fields 1.2.1 An address must have street name and city 1.2.2 Zip code must be 5 character numbers 1.3 If a user clicks on “submit” button without entering name and address fields, prompt the user with “you must enter your name and address to continue” 1.4 If a user is a returning user, pre-populate the existing user name and address 1.5 Provide ability to store the name and address fields as part of the customer records 1.6 Provide ability to submit the name and address page in less than 1 seconds 1.7 Provide ability to report on for manual re-entry by Support team, when the customer submits the name and address field and data is not successfully written in customer records 1.8 The systems should be able to handle 1 million concurrent transaction with no degradation in performance Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 17

Characteristics of Good Requirements Complete and Comprehensive Consistent Traceable, verifiable, testable Clear and unambiguous Modifiable Prioritized Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 18

Systems Requirement - Example No. Requirement Type Prior ity Must Have? 1 Provide ability to collect name and address from the end users 1.1 Provide ability to enter person’s first name and last name in separate input fields Functi onal High Musthave 1.2 Provide ability to enter address, which would have Street number, Street name, city, and zip code in separate input fields Functi onal High Musthave 1.2.1 An address must have street name and city Functi onal Medi um Musthave 1.2.2 Zip code must be 5 character numbers Functi onal Low Nice-tohave 1.3 If user clicks on “submit” button without entering name and address fields, prompt user with “you must enter your name and address to continue” Functi onal Medi um Musthave 1.4 If a user is a returning user, pre-populate the existing user name and address Functi onal Medi um Nice-tohave 1.5 Provide ability to store the name and address fields as part of the customer records Functi onal High Musthave 1.6 Provide ability to submit the name and address page in less than 1 seconds Perfor mance Medi um Nice-tohave 1.7 Provide ability to report on for manual re-entry by Support team, if the customer submits the name and address field and data is not successfully written in customer records Operat ional High Musthave Address part of reporting 1.8 The systems should be able to handle 2 million concurrent transaction with no degradation in performance Perfor mance Medi um Musthave At least 1 Million Systems & Infrastructure Lifecycle Management 1 Vasant Kumar Notes 19

Requirements Gathering BRD from the Business and Users SRD includes implicit IT requirements including those related to interface, reporting, availability, reliability, etc. Gap Analysis – Considering Top Down (strategic) and Bottom up (functional) analysis of the system, function, people etc. Security Requirements related to – Data, transmission of data (PKI, HTTPS, SSL for example), authentication, authorization, access – Access to the systems, Fire walls etc. – Information protection Vulnerability Management Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 20

Requirement Phase Best Practices Involve stakeholders (IT, User, Business) Avoid conflicting or not-achievable requirements Prioritize Use structured format Leverage Good Requirements characteristics Include systems implicit requirements (operational, interface, quality), which are typically not easily comprehended by the users/Business Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 21

Use Case What does Use Case do? Helps in defining Requirements by how users would interact with the system Provides a practical way to decompose and come up with the requirements Often helpful on a complex project Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 22

Use Case Example Name: Entering Name and Address Identifier: Use Case #10 Description: This use case captures how a user would enter name and address as part of the web ordering for a preregistered user Pre-condition: User must have clicked on “order” button on the home page and user is not a pre-registered user Steps: 1. User comes to the Personal information screen 2. The system validates the user is not a pre-registered user 3. Systems paints the name and address fields 4. User would enter first and last name 5. User would enter street name and city 6. User would enter street number and zip-code (optional fields) 7. User clicks submits 8. System stores name and address data 9. Systems shows the name and address was completed and paints “product” screen 8. Alternate course 10.1 for Edits on the screen 9. Alternate course 10.2 for data not stored in the database Post-condition: The user name and address data is now stored Alternate Cases: 10.1 (Edits fails): 1. Systems prompts user to enter incomplete field Alternate Cases: 10.2 (Name and Address data could not be stored): 1. Systems prompts user to contact customer service representatives with phone number Notes: this use is part of the ordering flow Additional Use Case Reference: se.htm Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 23

Auditing Requirements Definition Obtain the requirements artifacts such BRD (Business Requirements Document) and SRD (Systems Requirements Document) Adequate participation from the key stakeholders: Business, IT (Requirements and Design teams specifically), and Users Ensure BRD and SRD meet quality guidelines. The best Systems Requirements are detailed, clear (unambiguous), consistent, traceable, verifiable, modifiable, and prioritized. Review high-level design and architecture to ensure they meet the Business needs and “reasonably” correspond to the BRD/SRD Determine if application is a candidate for the use of an embedded audit routine Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 24

Question Requirements can be gathered by all except the following A. Developing a mock system or prototype B. Interviewing users, business, and IT teams C. Speaking to Vendors to understand which software is selling well in last two years D. Getting an understanding on what other companies did in a similar situation Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 25

Upcoming Assignments/Tests 1. Quiz 1 (Business Case Development, Project Management Practice, Develop Project Control, etc. Materials covered ion the first 4 Classes – 1/14, 1/21, 1/28, 2/4). Multiple Choice CISA Exam type questions: Thu 2/11 2. Group Project -1 (Business Case, RFP): Thu 2/18 before the class Questions? Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 26

Summary of Today’s Class Traditional SDLC SDLC Phases Variants Requirement Phase Focus of the Next Class and Reading Questions Systems & Infrastructure Lifecycle Management 1 Vasant Kumar 27

CISA SDLC Phases and Relationship 4 Phase 1 - Feasibility Phase 2- Requirements Phase 3 A-Design Phase 3B- Selection Phase 4A - Development Phase 4B- Configuration Phase 6 -Post Implementation Phase 5 - Implementation Build Buy Reviews at the end of each phase acts as "stage gate"

Related Documents:

MIS 617 Computers and Management Information Systems MIS 625 Management Information Systems MIS 673 Information Systems Development and Implementation MIS 674 Corporate Data Management MIS 675 Contemporary MIS Topics MIS 685 Data Base Management Systems MIS 690 Advanced MIS Seminar MIS 277, MIS

(prorated 13/week) week 1 & 2 156 week 3 130 week 4 117 week 5 104 week 6 91 week 7 78 week 8 65 week 9 52 week 10 39 week 11 26 week 12 13 17-WEEK SERIES* JOIN IN MEMBER PAYS (prorated 10.94/week) week 1 & 2 186.00 week 3 164.10 week 4 153.16 week 5 142.22 week 6 131.28 week 7 120.34

1.1.2.4 Design Standards This Design Standard references the following component standards MIS 01 Street planning and design MIS 04 Subsurface drainage MIS 05 Active travel facilities design MIS 06 Verges MIS 07 Driveways MIS 08 Stormwater MIS 11 Off street Parking MIS 15 Urban Edges Management Zone MIS 16 Urban open space

Week 3: Spotlight 21 Week 4 : Worksheet 22 Week 4: Spotlight 23 Week 5 : Worksheet 24 Week 5: Spotlight 25 Week 6 : Worksheet 26 Week 6: Spotlight 27 Week 7 : Worksheet 28 Week 7: Spotlight 29 Week 8 : Worksheet 30 Week 8: Spotlight 31 Week 9 : Worksheet 32 Week 9: Spotlight 33 Week 10 : Worksheet 34 Week 10: Spotlight 35 Week 11 : Worksheet 36 .

Mi madre, la figura más importante de mi vida. Que Dios la bendiga. Mis hermanos, que fueron siempre mis mejores educadores. La compañera de mi vida y de mis sueños, mi querida esposa Asraa Mis cuatro ángeles, mis hijos Mohamed, Yusuf, Sara y Muhanned. Todos mis amigos, quienes compartieron mis sueños y deseos.

28 Solving and Graphing Inequalities 29 Function and Arrow Notation 8th Week 9th Week DECEMBER REVIEW TEST WEEK 7,8 and 9 10th Week OCTOBER 2nd Week 3rd Week REVIEW TEST WEEK 1,2 and 3 4th Week 5th Week NOVEMBER 6th Week REVIEW TEST WEEK 4,5 and 6 7th Week IMP 10TH GRADE MATH SCOPE AND SEQUENCE 1st Week

Year 4 negative numbers. digit numbers by one digit, integer Year Group Y4 Term Autumn Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10 Week 11 Week 12 Number – place value Count in multiples of 6, 7, 9. 25 and 1000. digits using the formal writt

WRM –Year 6 –Scheme of Learning 2.0s Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10 Week 11 Week 12 tumn Number: Place Value N