{"id":3597,"date":"2018-02-28T18:44:00","date_gmt":"2018-02-28T23:44:00","guid":{"rendered":"http:\/\/community.mis.temple.edu\/mis5203sec951sp2018\/?page_id=3597"},"modified":"2018-04-05T17:04:10","modified_gmt":"2018-04-05T21:04:10","slug":"319-am-requirements","status":"publish","type":"page","link":"https:\/\/community.mis.temple.edu\/mis5205bnai2018\/319-am-requirements\/","title":{"rendered":"3\/19 AM – Requirements"},"content":{"rendered":"

Requirements Analysis<\/h2>\n

\u201cSystems analysis is the part of the systems development life cycle in which you determine how the current information system functions and assess what users would like to see in a new system. Analysis has two subphases: requirements determination and requirements structuring. In this unit, you will learn about determining system requirements. Techniques used in requirements determination have evolved over time to become more structured and increasingly rely on computer support. We will first study the more traditional requirements determination methods, including interviewing, observing users in their work environment, and collecting procedures and other written documents. We will then discuss more current methods for collecting system requirements. The first of these methods is Joint Application Design (JAD). Next, you will read about how analysts rely more and more on information systems to help them perform analysis. As you will see, CASE tools, discussed in unit one, are useful in requirements determination, and prototyping has become a key tool for some requirements determination efforts. Finally, you will learn how requirements analysis continues to be an important part of systems analysis and design, whether the approach involves business process redesign, new Agile techniques (such as constant user involvement or usage-centered design), or focuses on developing Internet applications.\u201d<\/span><\/p>\n

Valacich, J. S., & George, J. F. (2017).\u00a0<\/span>Modern systems analysis and design <\/span><\/i>(8th ed.). Boston: Pearson.<\/span><\/p>\n

In this unit, we will also discuss object oriented techniques for analysis and design. \u00a0The modeling mechanisms and syntax are fully defined in the Unified Modeling Language (UML) standards, which have their origins in object oriented software systems design. \u00a0Although they were originally intended as a tool for software development, their usefulness and flexibility for modeling any digital infrastructure have facilitated their becoming the defacto standard models used in systems analysis and design as well.\u00a0 One UML model that is useful in in the requirements determination phase is the “use case”, which will be covered in this unit.<\/span><\/p>\n

Activities<\/h3>\n