IT4683/IT6683 Management of IT IT6423 IT Systems Acquisition and Integration Exercise 2- IT Systems Acquisition Lifecycle and Business Process Modeling Developed by Richard Halstead-Nussloch Version...

1 answer below »
I need help completing this assignment ,I have been overwhelmed in other classes and need your help.


IT4683/IT6683 Management of IT IT6423 IT Systems Acquisition and Integration Exercise 2- IT Systems Acquisition Lifecycle and Business Process Modeling Developed by Richard Halstead-Nussloch Version 01Sep18 Your name: Policies: · Submissions made through a means other than the D2L Assignment Folder will be ignored and earn a 0. · Submissions without your name stated above earn a 0. · Submissions with the original questions and/or formatting removed from the file earn a 0. · Submissions without adequate references or acknowledgements will earn a discounted grade, potentially a 0. · Submissions that I can not open or require a password will earn a 0. · Second chances might be requested at any time through D2L email, and are awarded at the sole discretion of the instructor. Submissions should use and cite at least one reference and explicitly state who is being acknowledged. Put them in the end of this exercise document in the appropriate sections. Section 1 IT Systems Acquisition Lifecycles (SALC) Deliverables: · Three questions answered below. · Entry on discussion for IT Lifecycles · Entry on your Personal BLOG Q1) (20 Points) Review and analyze systems and SALC terms and concepts in relationship to IT. Wikipedia in https://en.wikipedia.org/wiki/Systems_engineering defines systems engineering as an interdisciplinary field that “focuses on how to design and manage systems over their life cycles.” We will use this as a point of departure for understanding the IT SALC. Please complete the development of a list of the top ten words or concepts the IT professional should know along with their definitions about the IT SALC. Add six terms/concepts to those there already. 1. System- 2. IT System- 3. Systems engineering- an interdisciplinary field that “focuses on how to design and manage systems over their life cycles.” [1] 4. IT SALC- 5. Etc. Q2) (20 Points) In 2 pages compare and contrast between two and four typically used IT system acquisition life cycles (SALCs), e.g., those based on Agile versus Waterfall or DAU versus ISO versus DOAS. Utilize life cycles you have learned in other courses and on the job in addition to the life cycles covered in this course. Embed your comparison and contrast here. (Hint: use a table.) Don't forget to cite your references! Q3) (20 Points) Develop about five Powerpoint slides to include your top 10 from question 1 and your main points of comparison and contrast for question 2 above. Post these slides to the discussion on IT Lifecycles along with some notes to cover in presenting them. Also, upload the PowerPoint file to the A2 folder along with this assignment file. As you think about these matters, try to find connections among the Lifecycles, IT business value, IT sourcing, etc. Also post your slides and any comments to the LM2 Discussion Topic for Slides for SALC terminology and comparing IT SALCs. Don’t forget to cite your references! Section 2 Business Processes and IT Deliverables: · Two questions answered below. · Discussion entries on D2L about business processes and IT. Q4) (20 Points) The module has made the point that, in order for the implementation of in particular larger IT and software applications, such as enterprise systems or customer relationship management systems, an organization often has to adopt the processes embedded in the software. Historically within IT, business processes and their understanding play a major role in the success of IT systems. Do a library search (note, exploring the optional Educause articles at the end of the LM2 Readings Readme qualifies here) and find an article that discusses at least one of the following three main points of the textbook here: · Distinguish between different types of business process · Discuss the relationship between business processes and IT · Discuss change management issues pertinent to business processes Include a one-page summary of this article here including how it addresses at least one of the three points above and post your views to the discussion topic on BPM in IT. Don’t forget to cite your references! Q5) (20 Points) In one paragraph, answer the question: “When deciding questions about whether IT systems acquisition and integration, senior IT professionals must pay attention to the SALC applied and the business processes involved because…” Provide your answer here and also in an entry on your personal Blog for this course. Don’t forget to cite your references! Sources and works used in completing this exercise: 1. Wikipedia article on Systems Engineering (retrieve September 1, 2018) https://en.wikipedia.org/wiki/Systems_engineering (Please add your references. You must list at least one and use the method-ACM, APA or MLA-chosen at the beginning of the term.) Please complete the following: ___ I did not use any method of citation (maximum B on the assignment). ___ I used the ACM approach and have cited my references as I went in the text and also listed them at the end. ___ I used the APA approach and have cited my references as I went in the text and also listed them at the end. ___ I used the MLA approach and have cited my references as I went in the text and also listed them at the end. Acknowledgements of people (and other exercise submissions) used in completing this exercise: (You might at least acknowledge the students with whom you’ve discussed the LM2 topics.) Readings ReadMe for LM2-IT6423 Curated by Rich Halstead-Nussloch 02Sep18 The IT6423 Story So Far… In LM0/A0, we aligned the IT6423 course objectives with Van Grembergen’s [1] three main IT governance principles which loosely stated are: 1) Provide value; 2) Do no harm; 3) Control IT. In LM1/A1, we saw the technology base of IT is continually advancing, which means IT professionals need to be able to discuss and apply: a) how IT is related to business and organizational strategy; b) how IT is critical to the success of most business models today; c) how the critical role of IT in the Value Chain [2] is less understood and recognized than the Value Chain itself; and d) there is a wide and diverse range of options for sourcing IT today with each option having its own advantages, disadvantages, risks, constraints, etc. 1. Van Grembergen, W. The Balanced Scorecard and IT Governance. IT Governance Institute Study Card (retrieved August 5, 2018) http://www.isaca.org/Certification/CGEIT-Certified-in-the-Governance-of- Enterprise-IT/Prepare-for-the-Exam/Study-Materials/Documents/The-Balanced- Scorecard-and-IT-Governance.pdf 2. Wikipedia article on the Value Chain (retrieved August 29, 2018) https://en.wikipedia.org/wiki/Value_chain Part 1: Articles on IT Systems Acquisition Life Cycles (SALCs) First, understand that the knowledge foundation and application of (IT) Systems Acquisition is diverse and also continually growing and expanding: Some Terms in a “Word Soup” To understand IT systems acquisition, one generally begins by making and then eating some, what I call, “word soup,” which is a set of terms, concepts, words and phrases that have all been thrown together at KSU in a broth brewed from Southern-American-English stock. Starting with system Wikipedia defines it as “a regularly interacting or interdependent group of units forming an integrated whole” (https://en.wikipedia.org/wiki/System). One would then expect IT system to be something like, as “a regularly interacting or interdependent group of IT units forming an integrated whole system for processing information.” But, no deal; as of today, Wikipedia does not have a page for “information technology system.” Instead it offers the reader a generic page covering IT (https://en.wikipedia.org/wiki/Information_technology) or a page covering “information system” (https://en.wikipedia.org/wiki/Information_system). Searching more words for LM2, system development is defined as the Systems Development Life Cycle or SDLC (https://en.wikipedia.org/wiki/Systems_development_life_cycle) and the search for system acquisition or Systems Acquisition Life Cycle (SALC) circles back to SDLC. Looking back to IT sourcing strategies and LM1, historically within IT the SDLC has been used for “make” projects and the SALC has been used for “buy” projects. There are also other conceptual word http://www.isaca.org/Certification/CGEIT-Certified-in-the-Governance-of-Enterprise-IT/Prepare-for-the-Exam/Study-Materials/Documents/The-Balanced-Scorecard-and-IT-Governance.pdf http://www.isaca.org/Certification/CGEIT-Certified-in-the-Governance-of-Enterprise-IT/Prepare-for-the-Exam/Study-Materials/Documents/The-Balanced-Scorecard-and-IT-Governance.pdf http://www.isaca.org/Certification/CGEIT-Certified-in-the-Governance-of-Enterprise-IT/Prepare-for-the-Exam/Study-Materials/Documents/The-Balanced-Scorecard-and-IT-Governance.pdf https://en.wikipedia.org/wiki/Value_chain https://en.wikipedia.org/wiki/System https://en.wikipedia.org/wiki/Information_technology https://en.wikipedia.org/wiki/Information_system https://en.wikipedia.org/wiki/Systems_development_life_cycle nuances (https://www.quora.com/What-is-the-difference-between-software-development-life- cycle-and-system-development-life-cycle) that we can cover in making our word soup here. Please spend 10 to 30 minutes searching the web to get a grasp on this word soup for system, IT system, system development, system acquisition, SDLC, SALC, etc. Systems Engineering is the Foundation for the SALC To move forward, we begin by noting that today’s IT systems are the descendants of more general manufactured systems; the development and acquisition of such systems has been studied in the field of systems engineering (https://en.wikipedia.org/wiki/Systems_engineering) since World War II. Our modern phone and Internet networks, success in the space race, victory in war, etc. would not be possible without “systems thinking” and disciplined systems engineering. Of the organizations that utilize systems engineering to acquire (IT) systems, the U.S. Military is a thought and practice leader. As a matter of fact, they have a university devoted to acquisition- the Defense Acquisition University or DAU (https://www.dau.mil/). The DAU press has made available an online reference book, Systems Engineering Fundamentals, and since it is in the public domain, a pdf copy (from http://www.dtic.mil/dtic/tr/fulltext/u2/a606327.pdf) is contained in D2L LM2. We suggest that you skim through the Table of Contents and then read closely the Preface through Chapter 3 (ending on page 34). Pay close attention to:  Figure 1-4 (page 8) and the descriptions of the Primary Life Cycle Functions (pages 7-8)  Figure 2-1 (page 12) showing the time flow of the standardized Defense Acquisition Process (A) Concept; B) Development; C) Production; D) Sustain and Dispose). Chapter 2 (pages 11-22) shows the overview and then details each of the Milestones A-D.  Supplement 2A (pages 23-24) show an ordinal scale of Technology Readiness. Read through this and reflect on your answer to Question 2 of Exercise A1, where you analyzed IT technologies for Higher Education over the past five years. Could your analysis table benefit from an additional column showing the Readiness of those technologies on this scale?  Chapter 3 (pages 31-34) covers an overview of the Systems Engineering Process. By focusing on Figure 3-1 (page 31), one obtains a process-flow-perspective SALC with Inputs; (Four Major) Categories of Sub-Processes (Requirements Analysis, Function Analysis and Allocation, Synthesis, and Systems Analysis and Control for Balance); and Outputs.  Finally, step back and read Supplement 2B (pages 25-28) on Evolutionary Acquisition. Reflect back on Moore’s Law from LM1 as this supplement helps us understand how to deal with rapid advancements in technology for our IT systems. Details on Getting from Point A to Point C Historically in IT
Answered Same DayFeb 06, 2021

Answer To: IT4683/IT6683 Management of IT IT6423 IT Systems Acquisition and Integration Exercise 2- IT Systems...

Neha answered on Feb 10 2021
142 Votes
50406/PPT.pptx
IT Software Acquisition Life Cycle
Submitted by:-
IT SALC
A system can be defined as a group of interrelated entities which interact with each other and form a whole. A system comprises of the boundaries and it is surrounded by the environment. We can describe a system based on its functioning. A system comprises of multiple views and system model is required to understand all the views of a system.
Subsystem can be defined as the set of elements. It is a part of a larger system and acts as a system itself. A subsystem has the capability to int
eract with the remote and local operators.
IT system stands for the information technology. It uses the computers to store, modify, retrieve and even to transmit any data or information. It is considered as the subset of information communication technology. It is used for the business operations.
The IT systems are an information system or computer system which includes hardware, software and some peripheral equipment used by some users.
IT SALC
System development can be defined as the process of defining, designing, developing, testing and implementing any new application or changes in any existing system. The system development can be internal development like creating database systems or it can be third party software development. To have the effective system development, we need to make sure that the system has predefined costs, benefits, goals and other things. To have a successful system all steps must be followed by the developers.
System Engineering can be defined as the interdisciplinary field of engineering and the management which focuses on the method of designing and managing the complex systems. It works on every life cycle of a project. It is an integrative approach to enable a successful realization, uses, system principles and concepts.
IT system acquisition life cycle can be defined as the standard process to define the process and flow of the development of a system. The SALC follows waterfall model. There are multiple steps in the life cycle of developing a system.
IT SALC
Waterfall model is a process in which the flow of process flows steadily downwards. It follows all the stages of the life cycle.
Requirement analysis lets the manager analysis the system and finalize all the requirements in the terms of resources, money, time or developers.
System design makes the developer to design the system and discuss it with the client so that he can give confirmation regarding the same.
Implementation phase is to implement the system as per the design.
Testing is done to make sure that developed system is working as per the initial design and it does not fail unless there is a hardware crash.
Deployment is the process of handing over the system to the client and installing it on their hardware.
Maintenance of the system is very important. The developers help the client with this part in the future. System acquisition can be defined as the process of going through the steps of developing a system.
Waterfall Model And Agile Model
The waterfall model can be defined as the step by step approach to the development of a software. This means that it includes all the steps starting from the conception to the implementation of the project. It is a traditional approach for developing any system and still used by some organisations.
The agile model came later than the waterfall model. This method breaks the stages of development life cycle into incremental order and builds the system on successive stages known as sprints.
Comparison
                 Waterfall Model        Agile Model
        Definition        The waterfall model is a traditional model of developing any system and it moves steadily downwards to complete the development of any system following the stages.        The agile model is newer as compared with the waterfall model but not the latest. It moves in an incremental order and follows all the stages. It divides the work into parts which are known as the sprints.
        Advantages        Clear Framework- This provides a clear image about the project timeline and the requirements of the customer.
Documentation- A clear documentation is done for the requirements of the system which eliminates the chance of confusion and it is shared with the client.
Flexible Team- The developers for the system can be added or removed any time during the life cycle of the project depending upon the requirements.         Flexible Deliverables- It allows the stakeholders to deliver the project as per the importance of that part.
Adaptability- It is a crucial element of this model. The customer can change the requirements after seeing the software and changes can be made at that stage itself.
Higher Quality- It provides better quality products. Since the customers share their feedback at every sprint, it becomes easier to make the changes.
        Disadvantages        Lack Of customer Interaction
Changes are difficult
Last minute changes        Required Commitment
Potential for higher cost
Communication
Thank you
50406/Report.docx
Section 1
Q1)
IT System Acquisition Lifecycles
This report is to understand the Lifecyle of IT system acquisition. To understand this concept, we have to proceed word by word.
The first word is System. A system can be defined as a group of interrelated entities which interact with each other and form a whole. A system comprises of the boundaries and it is surrounded by the environment. We can describe a system based on its functioning. A system comprises of multiple views and system model is required to understand all the views of a system.
Subsystem can be defined as the set of elements. It is a part of a larger system and acts...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here