Subject Program. Subject/Module : Engenharia de Software e Gestão de Projectos de Saúde. Year : 2º Semester : 2º School Year : 2010/2011

Transcription

1 1 de :17 Printed on: :17:55 Subject Program Subject Identification Organic Unity Course : [IS] Informática para a Saúde Degree : Subject/Module : Engenharia de Software e Gestão de Projectos de Saúde Kind : required Scientific Field : Information Systems ECTS : 6 Year : 2º Semester : 2º School Year : 2010/2011 Prerequisites : Not applicable. Hours Of Workload Theory Classes (TC) 30:00 Practical Laboratory (PL) 45:00 Tutorial (T) 5:00 Hours of Autonomous Work 82:00 Horas Totais 162:00 Lecturing Language Portuguese and English Lecturers Main Lecturer : Rui Pedro Charters Lopes Rijo Lecturers Pedro Romeu Henriques Ferreira Rui Pedro Charters Lopes Rijo Framework The course works on soware engineering, with emphasis on specificaon, development and validaon of crical soware, and the use of processes, techniques and tools in planning and implementaon of soware projects in healthcare. Objectives/Skills General

2 2 de :17 CG1. Analyze and design critical software correlated with the area of Healthcare Information Systems; CG2. The use of techniques and software tools to specify software, particularly in the disciplines of requirements engineering, design and software development; CG3. Software testing; CG4. Planning and managing software projects. Specific CG1. Analyze and draw critical software correlated with the area of Health; CE1. Identify vulnerabilities in a system CE2. Identify the critical requirements in systems CE3. Using the techniques and tools for designing critical software CE4. Justifying the options assumed in the design of a system CG2. Using techniques and tools for specifying software, including the disciplines of requirements engineering, design and software development; CE5. Using the concepts of modularity and abstraction CE6. Using the main software design patterns CE7. Taking design options, knowing the consequences and aligning them with organizational goals CG3. Perform software testing; CE8. Draw unit testing and system integration CE9. Using the tools necessary for the achievement of the tests CE10. Documentation of software testing CG4. Planning and managing software projects.

3 3 de :17 CE11. Specify the scope of a project CE12. Estimate the time and cost of a project CE13. Define the quality of a project Transversal CT1. Analyzing and reasoning CT2. Ability to plan and carry out projects CT3. Leadership skills CT4. Ability to study independently CT5. Ability to work in team Contents Synopsis 1. Soware development processes 2. Requirements idenficaon and specificaon 3. Soware design 4. Tests 5. Project management soware Complete 1. Software development processes 1.1. Waterfall

4 4 de : ICONIX 1.3. XP - Extreme Programming 1.4. Rational Unified Process 2. Survey and specification requirements 2.1. Software Requirements 2.2. Formalization of software requirements 2.3. Specification of critical systems 2.4. Formal specifications 2.5. UML diagrams 3. Software design 3.1. Systems Modelling 3.2. Object-oriented design 3.3. Architectural Drawing 3.4. Component-based software 3.5. Software reuse 3.6. Development of software 4. Tests 4.1. Verification and validation 4.2. Unit tests

5 5 de : System testing 4.4. Integration tests 5. Project Management Software 5.1. Time management, human resources, scope and cost of software projects 5.2. Quality management and risk in software projects in the area of??health 5.3. Configuraon management Demonstration of the coherence of the contents with the objectives/skills of the subject The unit of Software Engineering and Project Management for Healthcare Information Systems seeks to provide students with the foundations of the development of software for healthcare systems. It also aims to teach the principles of project management in this sector. Thus, the concepts are introduced based on survey and requirements specification, software design, testing, configuration management and version and entry into production software. These elements are also presented from the perspective of project management, including the evaluation of projects, preparation of work plans, time and budget, determining the critical path, risk management, communication and human resources. Are also presented the main processes and functional areas of health organizations that support business development projects in health informatics. We can relate the following topics detailed program, with each of the following specific responsibilities: 1.1. Waterfall: CE4. Justifying the options assumed in the design of a system 1.2. ICONIX: CE4. Justifying the options assumed in the design of a system 1.3. XP - Extreme Programming: CE4. Justifying the options assumed in the design of a system

6 6 de : Rational Unified Process: CE4. Justifying the options assumed in the design of a system 2.1. Software requirements: CE2. Identify the critical requirements in a system; CE4. Justifying the options assumed in the design of a system; CE11. Specify the scope of a project 2.2. Formalization of software requirements: CE2. Identify the critical requirements in a system; CE4. Justifying the options assumed in the design of a system; CE11. Specify the scope of a project 2.3. Specification of critical systems: CE1. Identify vulnerabilities in a system; CE2. Identify the critical requirements in a system; CE4. Justifying the options assumed in the design of a system; CE11. Specify the scope of a project 2.4. Formal specifications: CE1. Identify vulnerabilities in a system; CE4. Justifying the options assumed in the design of a system; CE11. Specify the scope of a project 2.5. UML diagrams: CE2. Identify the critical requirements in a system; CE4. Justifying the options assumed in the design of a system; CE5. Using the concepts of modularity and abstraction; CE6. Using the main software design patterns; Ne7. Taking design options, knowing the consequences and aligning them with organizational goals; CE11. Specify the scope of a project 3.1. Systems Modelling: CE2. Identify the critical requirements in a system; CE4. Justifying the options assumed in the design of a system; CE5. Using the concepts of modularity and abstraction; CE6. Using the main software design patterns; Ne7. Taking design options, knowing the consequences and aligning them with organizational goals 3.2. Object-oriented design: CE3. Using techniques and tools for software design critic, EC4. Justifying the options assumed in the design of a system; CE5. Using the concepts of modularity and abstraction; CE6. Using the main software design patterns; Ne7. Taking design options, knowing the consequences and aligning them with organizational goals 3.3. Architectural Drawing: CE3. Using techniques and tools for software design critic, EC4. Justifying the options assumed in the design of a system; CE5. Using the concepts of modularity and abstraction; CE6. Using the main software design patterns; Ne7. Taking design options, knowing the consequences and aligning them with organizational goals 3.4. Based software components: CE3. Using techniques and tools for software design critic, EC4. Justifying the options assumed in the design of a system; CE5. Using the concepts of modularity and abstraction; Ne7. Taking design options, knowing the consequences and aligning them with organizational goals 3.5. Software reuse: CE3. Using techniques and tools for software design critic, EC4. Justifying the options assumed in the design of a system; CE5. Using the concepts of modularity and abstraction; CE7. Taking design options, knowing the consequences and aligning them with organizational goals 3.6. Evolution of software: CE3. Using techniques and tools for software design critic, EC4. Justifying the options assumed in the design of a system; CE5. Using the concepts of modularity and

7 7 de :17 abstraction; CE7. Taking design options, knowing the consequences and aligning them with organizational goals 4.1. Verification and validation: CE1. Identify vulnerabilities in a system 4.2. Unit tests: CE1. Identify vulnerabilities in a system; CE4. Justifying the options assumed in the design of a system; CE8. Draw unit testing and system integration; CE9. Using the tools necessary for the achievement of the tests 4.3. Test system: CE1. Identify vulnerabilities in a system; CE4. Justifying the options assumed in the design of a system; CE8. Draw unit testing and system integration; CE9. Using the tools necessary for the achievement of the tests 4.4. Integration tests: CE1. Identify vulnerabilities in a system; CE4. Justifying the options assumed in the design of a system; CE8. Draw unit testing and system integration; CE9. Using the tools necessary for the achievement of the tests 5.1. Time management, human resources, scope and cost of software projects; CE4. Justifying the options assumed in the design of a system; CE11. Specify the scope of a project; CE12. Estimate the time and cost of a project 5.2. Quality management and risk in software projects in the area of??health: CE1. Identify vulnerabilities in a system; CE4. Justifying the options assumed in the design of a system; CE13. Define the quality of a project 5.3. Configuration management: CE4. Justifying the options assumed in the design of a system; CE7. Taking design options, knowing the consequences and aligning them with organizational goals Teaching/Learning Methodology Contact and Autonomous The learning methodology is developed through the following components: face 1. theorecal

8 8 de : Presentaon of concepts 1.2 Exemplificaon and applicaon to real problems 2. Theorecal and praccal 2.1 Modeling and solving problems 2.2 Crical analysis of the problems and their soluons 3. Praccal and laboratory 3.1 Conducng exercises illustrang the principles 3.2 Development of praccal work 4. tutorial 4.1 personal coaching sessions in small groups to conduct the learning process and clarify doubts autonomous 1. study 1.1 Reading of excerpts from the course recommended readings 1.2 Resoluon of the recommended exercises 2. E-learning

9 9 de : Consultaon material of the course Specific Resources 1. Theorecal - regular classroom 3. Praccal and laboratory - Laboratory of Informacs 4. Tutorial - cabinet or the regular classroom Demonstration of the coherence of the teaching/learning methodology with the objectives/skills of the subject The teaching methods used contribute to the general powers set out to UC the following: face 1. theorecal 1.1 Presentaon of the concepts - (C1 and C4) 1.2 Exemplificaon and applicaon to real problems - (C1, C2, C3 and C4) 2. Theorecal and praccal 2.1 Modeling and problem solving - (C2 and C3) 2.2 Crical analysis of problems and soluons - (C2 and C3) 3. Praccal and laboratory 3.1 Conducng exercises illustrang the principles-(c2, C3 and C4)

10 10 de : Development of praccal work - (C2, C3 and C4) 4. tutorial 4.1 personal coaching sessions in small groups to conduct the learning process and clarify doubts - (C1, C2, C3 and C4) autonomous 1. study 1.1 Reading of excerpts from the recommended reading course - (C1, C2, C3 and C4) 1.2 Resoluon of the exercises recommended by the course - (C1, C2, C3 and C4) 2. E-learning 2.1 Consultaon material of the course - (C1, C2, C3 and C4) Assessment Description The methods evaluaon are the following: PERIODIC EVALUATION Two individual wri9en tests (PEI1, PEI2) with minimum of 9.5 values. A praccal work (TP) with a minimum of 9.5 values. Final Rang: 0.25 * PEI * PEI *TP

11 11 de :17 FINAL EVALUATION Final individual written exam (PEI) and practical test (PP). Final Rating: 0,5*PEI + 0,5*PP Number of Evaluations Continuous/Periodic 3 Final 2 Bibliography Main Ian Sommerville, Software Engineering, Addison-Wesley, 2010 Hassan Gomaa, Software Modeling and Design: UML, Use Cases, Patterns, and Software Architectures, Cambridge University Press, Alberto Silva e Carlos Videira, UML - Metodologias e Ferramentas CASE, Centro-Atlântico, António Miguel, Gestão de Projectos de Software, FCA, Complementary Approval Approved by CTC in :