Abstract - Enterprise Architecture can be a means to achieve IT governance, what
ensures a competitive advantage to organization. However, after dozens
years of studies, researchers have inferred about the approaching be
immature. There also a big dispersion about its subjects and a bit
participation of the industry, while there are several troubles to solve
during their applying, which hinders the right alignment to enterprise
perspectives. This work, contributes to a hybrid approach, which inserts
into the architecture life cycle, a software process model based on
management models. In this context, this paper presents the FACTO, a
roadmap for institutionalizing, evaluating and implementing an
Enterprise Architecture within a software development environment.
Mostrando postagens com marcador Business Process Management. Mostrar todas as postagens
Mostrando postagens com marcador Business Process Management. Mostrar todas as postagens
domingo, 26 de fevereiro de 2012
domingo, fevereiro 26, 2012
Jaguaraci Silva
Architecture Framework, Business Process Management, Enterprise Architecture, FACTO, Framework, Governace, IT
No comments
sábado, 25 de fevereiro de 2012
sábado, fevereiro 25, 2012
Jaguaraci Silva
Business Process Management, COBIT, Enterprise Architecture, Governace, IT
No comments
FACTO Enterprise Architecture Framework
Is or is not the IT Governance ensured by the COBIT 5?
Among goals and objectives for supporting and using the COBIT as 4 as 5 within the IT Governance project, I will show a little vision that I have about it.
The Implementation of good practices usually is seen and drawn in a top-down approach, in which the vision of IT governance suggests their origin from executive board of firm, and does not to improve their business unit processes. In order to align the contained practices conjointly with Sarbanes Oxley law, therefore, the projects, which involves IT governance ever won’t run over communication, collaboration and commitment visions within the other company’s business units.
IT governance projects are driven to legal requirements, which are mandatory and don't particularly follows in a cooperative form. Normally it starts from the business process management, where there are three kinds of process: management, operational and support. The entire value chain of the firm needs to cross all these processes, whereas their collaboration is very important, in addition, the proper communication and commitment of people to achievement goals and objectives of these processes.
The COBIT or anywhere process model, depends on business process management, mainly to figure out the people that perform the key processes in the entire value chain, where the principles and standards will be defined in according to expected type of this practice in the business unit processes. Without collaboration, communication and commitment of the people, you cannot govern the whole firm.
Figure 1 – COBIT 5 draft (ISACA).
The Figure 1 shows how the COBIT 5 processes are in a high level of abstraction, i.e. define, align, and suggest, however, don't effectively carries on the activities. As matter as fact, all these activities, that only are suggest, will be performed automatically by the software systems or manually, based on knowledge of the people. Thus, the correct implementation of the software systems would be ensured only when the right instantiation of a IT governance model, what is a role of an enterprise architecture in the company.
In defense this argument, I will quote a few goals when someone wishes to implement enterprise architecture (coincidence or not is very similar that already cited by the COBIT’s principles):
1 – To make a connection between business requirements and IT projects and their software systems.
2 – To arrange a set of IT activities into a process model, which generally can be accepted by the people that
performing their activities in a holistic way.
3 – To identify the most important IT resources to being used in according with the business strategy and IT.
4 – To define a management objectives control to being considered avoiding the inadvertent use of IT resources.
segunda-feira, 20 de fevereiro de 2012
segunda-feira, fevereiro 20, 2012
Jaguaraci Silva
AS-IS, BPM, Business Process Management, Models, TO BE, Tutorial
No comments
A whole tutorial about Business Process Management or BPM. In this talking I have related the steps to perform process modeling AS-IS and TO-BE, techniques for finding information and how to align the whole thing on both: modeling business plan and company goals.
Finally, I have presented, in this video below, which models are more often used on market to perform a process evaluation and their improvement, well like how to measuring the business processes maturity by using good practices. In a simple and uncomplicated way to those who does not know or never have had the opportunity of enroled itself in any meeting about BPM.
After this attending, I argue that you should deepen your knowledge about BPM modeling using the BPMN notation for become yourself a process analyst.
After this attending, I argue that you should deepen your knowledge about BPM modeling using the BPMN notation for become yourself a process analyst.
Video Tutorial here!!
segunda-feira, 13 de fevereiro de 2012
segunda-feira, fevereiro 13, 2012
Jaguaraci Silva
BPM, Business Process Management, CMMI, Software Quality, SPEM
No comments
Abstract— With the globalization, the lack of documents standardization and agility on inquiry the norms in the guides as well as the Capability Maturity Model Integrated (CMMI), lead to the loss of competitiveness. In the effort for certifications, the agility becomes important to get and to apply the necessary norms that guarantee the processes quality of its. This paper proposes a modeling of CMMI processes areas using Business Process
Management (BPM) with goal to growth the agility and information reuse, being created an approach between CMMI and Software Process Engineering Metamodel Specification (SPEM) notations, to represent its components on the diagram forms, being sped up the understanding.
Management (BPM) with goal to growth the agility and information reuse, being created an approach between CMMI and Software Process Engineering Metamodel Specification (SPEM) notations, to represent its components on the diagram forms, being sped up the understanding.
Assinar:
Postagens (Atom)





