Assessment Brief: BIS2005 & SBM4303 Enterprise Architecture Trimester 2, 2021 Assessment Overview Assessment 1: Case Study Due date: Week 5 Group/individual: Group Word count / Time provided: 3500...

1 answer below »
Assessment 2 Report only


Assessment Brief: BIS2005 & SBM4303 Enterprise Architecture Trimester 2, 2021 Assessment Overview Assessment 1: Case Study Due date: Week 5 Group/individual: Group Word count / Time provided: 3500 Weighting: 30% (Report: 25% Presentation: 5% Unit Learning Outcomes: ULO1, ULO2, ULO3 Assessment Details: This case study will assess your knowledge of key content areas (Week 1, 2, 3, 4, 5 contents) and to identify further support needs. For successful completion of the case study, you are required to study Assessment Task Type Weighting Due Length ULO Assessment 1: Case Study Propose EA artifacts, taxonomy of documentations that to be delivered for a particular case study. In addition, to discuss the operating model and types of IT initiatives. Group 30% Report: 25% Presentation: 5% Week 5 3500 words (report and power point slides with embedded audio) ULO-1 ULO-2 ULO-3 Assessment 2: Report Write a report to examine the architecture function of a specific organisation and determining the operating model for a multi-profile company. The report should also cover the core concepts of data and information architecture and evaluate existing data and information architecture designs, continuity plans in the context of EA and role of audit and compliance standards in EA (details in the Assessment Brief). Individual 40% Week 12 3600 words ULO-3 ULO-4 ULO-5 Assessment 3: Quiz Every quiz will be conducted based on the teaching and learning materials covered in previous two weeks, for an example, quiz 1 in week 3 will be based on week 1 and week 2 teaching and learning materials (details in the Assessment Brief). Individual Invigilated 30% Week 2, 4, 6, 8 & 10 30 Minutes for each quiz (equiv. 750 words ) ULO-1 ULO-2 ULO-3 ULO-4 ULO-5 the material provided (lecture slides, tutorials, and reading materials), engage in the unit’s activities, and in the discussion forums. The prescribed textbook is the main reference along with the recommended reading material. By completing this assessment successfully, you will be able to identify key aspects of information systems. This will help in achieving ULO4. The case study will be completed and submitted in week 5. Case Study: SalesTech is a mid-size governmental department providing important services of a social nature to the population of a large territory. From the technology perspective, the organization can be considered as a late adopter of innovations and characterized by relative underinvestment in IT, which has certain implications for both its IT landscape and respective management practices. On the one hand, SalesTech’s IT landscape is very heterogeneous and includes many legacy information systems and technologies some of which have been in use for decades. On the other hand, its IT-related management practices are also rather archaic. For instance, the relationships between business and IT leaders in the organization exhibit evident signs of “us and them” mentality, while new investments in IT are viewed by business mostly as a means to reduce costs of the existing operations. SalesTech has a centralized IT department headed by the CIO and responsible for developing and supporting information systems for all its business units. The IT department employs around 140 specialists and consists of three main functions: architecture, development and service. The architecture function includes a few architects focused predominantly on specific IT solutions. SalesTech previously tried to uplift the maturity of its EA practice and extend the scope of architectural planning beyond separate initiatives, but these attempts failed and respective architects had been made redundant. Then, the CIO decided to undertake another deliberate effort to evolve SalesTech’s EA practice with the involvement of external consultants at Comserv. For this purpose, the organization engaged a rather well-known boutique EA consultancy (Comserv) to help initiate a full-fledged EA practice. The consultancy at Comserv formed a project team consisting of four architects specialized in different subject areas. This consulting team acted according to a detailed engagement plan agreed with SalesTech’s senior IT leadership. The plan stipulated in which sequence and when exactly various EA artifacts will be produced. In total, consultants worked for 2-4 months, analyzed the organization, interviewed numerous stakeholders and developed all the EA artifacts specified in the plan. Specifically, they started from analyzing SalesTech in terms of current and desired maturity of its business capabilities and mapped existing applications to respective capabilities. Then, they captured all relevant data entities, documented all technologies used in the organization, depicted current and defined target application portfolios and created more detailed CRUD (create, read, update and delete) relationship matrices. If you are Head of EA team at Comserv that SalesTech engaged; based on the case study above and EA lecture notes 1, 2, 3, 4 and 5: 1. Discuss five possible reasons why previously attempts to uplift the maturity of its EA practice and extend the scope of architectural planning beyond separate initiatives failed and what could be done to ensure that the evolvement SalesTech’s EA practice with external consultants would have a successful implementation of SalesTech’s EA practice. 2. Discuss four types of Enterprise Architecture Domains that you will implement first and why you considered the four domains to be most important to SalesTech’s EA practice 3. SalesTech’s team suggested that Comserv should implement Diversification EA operating models for them. However, your team at Comserv recommended that Coordination EA operating model should be implemented for SalesTech. Discuss 4 reasons why implementation of Coordination EA operating model is key to the success of SalesTech’s EA practice 4. Discuss 5 (five) key roles that Designs as an Enterprise Architecture artifact will play in SalesTech. 5. Discuss how Vision and Standard could be used at SalesTech’s if Comserv successfully implements of SalesTech’s EA? 6. Discuss 4 types of IT initiatives that you have considered very important to SalesTech’s EA 7. Describe the role of the 4 stakeholders in the EA implementation and SalesTech’s EA practice Marking Information: The case study will be marked out of 100 and will be weighted 30% of the total unit mark. Marking Criteria Not satisfactory (0-49%) of the criterion mark) Satisfactory (50-64%) of the criterion mark Good (65-74%) of the criterion mark Very Good (75-84%) of the criterion mark Excellent (85-100%) of the criterion mark Case Study Q1 (15% marks) Not able to discuss five reasons why implementation of EA practice could be a failure or successful Discussed five reasons why implementation of EA practice could be a failure or successful but details missing Most of the reasons identified and discussed but minor points are missing All the reason identified and discussed, provides very good reasons, examines the EA implementation clearly All the problems are clearly identified, provided excellent reasons, and examines the EA implementation clearly Q2 (15% marks) Discussed four types of Enterprise Architecture Domains but not properly discussed. Discussed four types of Enterprise Architecture Domains but details missing Discussed four types of Enterprise Architecture Domains in detail. Discussed four types of Enterprise Architecture Domains in detail, comprehensively examine the relation of EA Discussed four types of Enterprise Architecture Domains in detail, very comprehensively and excellently examine the relation of EA Q3 (10% marks Discussed 4 reasons why implementation of Coordination EA operating model is key to the success of SalesTech’s EA practice but lots of missing information Discussed 4 reasons why implementation of Coordination EA operating model is key to the success of SalesTech’s EA practice in SalesTech but details missing Discussed 4 reasons why implementation of Coordination EA operating model is key to the success of SalesTech’s EA practice in details. Discussed 4 reasons why implementation of Coordination EA operating model is key to the success of SalesTech’s EA practice comprehensively examine the relation of EA Discussed 4 reasons why implementation of Coordination EA operating model is key to the success of SalesTech’s EA practice very comprehensively examine the relation of EA Q4 (10% marks Discussed 5 (five) key roles that Designs as an Enterprise Architecture artifact will play in SalesTech but lots of missing information Discussed 5 (five) key roles that Designs as an Enterprise Architecture artifact will play in SalesTech but details missing Discussed 5 (five) key roles that Designs as an Enterprise Architecture artifact will play in SalesTech discussed in details. Discussed 5 (five) key roles that Designs as an Enterprise Architecture artifact will play in SalesTech comprehensively examine the relation of EA Discussed 5 (five) key roles that Designs as an Enterprise Architecture artifact will play in SalesTech in details, very comprehensively examine the relation of EA Q5 (10% marks Discussed how Vision and Standard could be used at SalesTech’s if Comserv successfully implements of SalesTech’s EA but lots of missing information Discussed how Vision and Standard could be used at SalesTech’s if Comserv successfully implements of SalesTech’s EA but few details missing Discussed how Vision and Standard could be used at SalesTech’s if Comserv successfully implements of SalesTech’s EA in detail. Discussed how Vision and Standard could be used at SalesTech’s if Comserv successfully implements of SalesTech’s EA and comprehensively examine the relation of EA Discussed how Vision and Standard could be used at SalesTech’s if Comserv successfully implements of SalesTech’s EA in details, very comprehensively examine the relation of EA
Answered 4 days AfterAug 24, 2021

Answer To: Assessment Brief: BIS2005 & SBM4303 Enterprise Architecture Trimester 2, 2021 Assessment Overview...

Neha answered on Aug 28 2021
149 Votes
Part 1
EA Software Tools
The enterprise architecture tools can be defined as the software applications which are designed supporting enterprise architects, IT stack holders and other business to plan, analyse, design and execute the project in strategic manner. These tools are able to support tactical decision making as they can capture and connect information and context across technology domains, information, solution and business along with the other related architectural viewpoints. The tool market has diverse range of the vendors. These vendors are providing software tools. These tools is used to offer the software which can enable enterprise architect to provide strategic planning
discipline and it is able to drive that targeted outcome of business. These tools are able to store, analyse and structure, and present the information related with enterprise architecture.
iServer is used for supporting large number of applications but few of the admin panels can not be accessed and it wastes a lot of time in making changes in the settings. The server is updated automatically, and we are able to share the files and commands without glitch.
Sparx system EA has easy steps in the initial stage and provides great features at the low cost. It is a great performer. The system development team you can use this enterprise architect tool as it is very flexible and allow the team to have to create and manage all the architectures four different applications. This tool is best to manage the requirements for any application.
Hopex it is the most comprehensive and easy to use modelling tool in the market. This tool is excellent for the enterprise architecture modelling and allow us to change the tracking. It helps us to keep our architecture up to date and also plan ahead for the new model. LeanIX EA Suite reviews Is another tool which is flexible and easy to use. This tool can be used for any type of enterprise architecture analysis.
It is the great tool and allow us to flexibly model the tool as per the requirement of organization. The organization is able to save significant amount of time to analyse the technical depth technology road map, business strategy planning and business capability mapping. The last tool is ABACUS, and it has great off standard features which should be present in enterprise architecture tool. It is highly customizable or configurable. With this tool the usability is at challenge. The user with technical modelling is able to use it but it will struggle for non-enterprise architect users. It has poor visualization and presentation.
How to increase usage of EA Tools
After installing the tool, it is important to make sure that the organization and relevant stakeholders are able to accept it and realise its benefits. The tool adoption can be quickly done, or it can be outright failed because of some common pitfalls.
There can be absence of proper communication or the implementation plan which can result in failure of adopting enterprise architecture tool. There can be misalignment of the tools capabilities as per the strategy of stakeholders. There might be need of over customising the model. The failure can be due to the lack of specialised talent which is required for the implementation and adoption. Avoiding these challenges is not easy, but it is critical to have the successful implementation of the tool. There are few basic steps which can be used for adopting the tool and make sure that people are using it in the organization.
· It is important to understand the environment. We can try to understand the regular processes and how the architecture matter data will be used to support the organization. We need to understand where and how the tool can be used to accelerate productivity, support the demands of stakeholders and increase quality.
· Try to convert the capabilities to service tax tsunami. The tool should be used to provide the core capabilities so that we can easily perform our work. We can classify the capabilities of the tool into service taxonomy so that the implementation has focus on the value propositions.
· We can build the community. We will provide the services to become the good service manager. We need to track the high and low which are experienced by the user community. We can use the social media approach to establish the community of the users. It will be easier to deal with the problems and users can't feel the sense of ownership accountability and commitment.
· We can try to plan, communicate and manage the expectations. When we are implementing and adopting the new technology then it needs to have a strong communication plan and change the management across all the stakeholders.
· Try to build the best team. The successful implementation can be done with the good team members.
Benefits of EA Tools
The enterprise architect tool can be used to have alignment between the business and people. If the company has focus over the digital business growth and also hold the values in compliance, security and privacy then it is important for them to have enterprise architecture program along with the professional tool. Hardly there is anyone in the sales who need to fight for the budget approval to have cloud-based customer relationship management solution yet there are many EA teams who struggle to get similar approach. This tool can be used to reduce the managerial risk. It provides the ease of understanding.
All the organizations have details about the business architecture, operating model and the application portfolio birth they are generally found to be scattered around, composed without central chip and owned by different stakeholders. It means that there are gaps between documented architecture and actual architecture. This can result in increased risk and non-compliance with the regulations. The enterprise architecture platform can help us to maintain the architecture up to date, visualise the future scenario impacts and communicate the complex analysis with the business executives in consistent manner.
Part 2
Major Roles
There are different roles which are generally studied for the enterprise architect artifacts. The considerations are defined as rules which are focused on the business. The enterprise architecture artifacts are related with the general type which are identified in the organization, and it includes policies, principles, code drivers, conceptual data models, position papers, white papers, strategy papers and governance papers.
All these are defects can be used to describe global conceptual rules and all the conditions which are important for business. They can be developed creatively with the help of senior business leaders and their architects. They have the goal to achieve the agreement of basic values, aims, directions and principles. The proper use of consideration can result in improved conceptual consistency.
Another one is standard which is focused on the...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here