| Code | DE0747 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Name | Enterprise Architecture and Requirements Engineering | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Status | Compulsory/Courses of Limited Choice | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Level and type | Post-graduate Studies, Academic | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Field of study | Computer Science | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Faculty | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Academic staff | Mārīte Kirikova, Pēteris Rudzājs | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Credit points | 6.0 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Parts | 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Annotation |
The study course presents basic approaches to requirements engineering. Students learn to identify and design enterprise/business architectures and specify requirements for organisational information systems viewing people and computer systems as nodes of information processing. They learn to analyse and evaluate information logistics in organizations. Acquired knowledge is beneficial not only for requirements identification for information and communication technology solutions; it is applicable also for the design of products and services in general. . |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Contents |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Goals and objectives of the course in terms of competences and skills |
The goal of the study course is to provide knowledge, understanding and skills in the identification, representation and management of requirements while respecting the enterprise architecture of organizations. The tasks of the study course: 1. To provide an understanding of business architecture and requirements engineering standards and their evolvement dynamics. 2. To provide awareness of the range of methods used in requirements engineering. 3. To develop the ability to reflect and evaluate enterprise architecture and its changes. 4. To develop the ability to use different requirements engineering methods and evaluate their usefulness in specific situations. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Learning outcomes and assessment |
Understands the goals, scope and problems of enterprise architecture and requirements engineering. - Demonstrate this understanding by solving tasks in the exam. Is able to acquire requirements without overstepping ethical principles of business, systems analysis, and information systems design. - Correct answers in individual or group assignments and/or the exam. Is able to use and evaluate requirements engineering methods and tools. - Correct answers in individual or group assignments and/or the exam. Is able to represent and evaluate the As-Is and To-Be states of an enterprise architecture. - Enterprise architecture models developed and evaluated in individual and/or group assignments and the exam. Is able to suggest systemic information technology solution according to the business needs. - Defines requirements for information technology solution systemically for the business needs of the case chosen in individual assignment and the case given in the exam. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Evaluation criteria of study results |
The results of individual and group assignments (at least 40% of the maximum of points should be achieved) - 50%
Exam (at least 40% of the maximum of points should be achieved) - 50% |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Course prerequisites | Suggested: systems analysis, database basics. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Course planning |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||