IISSI Presentation

Transcription

1 9/22/ Software Engineering and Databases Group Department of Computer Languages and Systems University of Seville Course learning objectives (I) When passed, the student should be able to: Understand the basics of software engineering. Understand the basics of software project management. Use project management and version control tools. Understand the basics of information systems. Introduction to Software Engineering and Information Systems 1 IISSI 1

2 9/22/2013 Course objectives (II) When passed, the student should be able to: Gather information about a not previously known problem domain. Develop a glossary of terms. Model simple business processes. Develop simple requirements. Develop simple conceptual models from requirements. Introduction to Software Engineering and Information Systems 2 Course objectives (III) When passed, the student should be able to: Understand the basics the relational data model, including 3NF. Use the SQL language on a commercial DBMS. Understand the concept of transaction. Understand the basics of query optimization. Introduction to Software Engineering and Information Systems 3 IISSI 2

3 9/22/2013 Course objectives (IV) When passed, the student should be able to: Develop simple user interfaces using HTML 5,CSS 3 and JavaScript. Work in groups on a project to develop a simple web application with access to a relational DBMS. Search and use technical documentation in English. Introduction to Software Engineering and Information Systems 4 Module I: Introduction to SE & IS Introduction to Software Engineering Software engineering basics. Software life cycle. Software requirements. Introduction to Project Management Work breakdown structure (tasks). Task planning. Time tracking (effort allocation). Version control. Introduction to Software Engineering and Information Systems 5 IISSI 3

4 9/22/2013 Module I: Introduction to SE & IS Introduction to Information Systems Information systems basics. Types of information systems. Business process modeling. Introduction to Software Engineering and Information Systems 6 Module II: Introduction to Databases Conceptual Modeling Requirements analysis. UML class diagrams (and ERD). Relational model Basic concepts of the relational model: AR, 3NF. MC MR transformation SQL: DDL, DML, queries. Transactions. Query optimization. Introduction to Software Engineering and Information Systems 7 IISSI 4

5 9/22/2013 Module III: Intr. to Application Development Web application development Client-side technologies: HTML 5, CSS 3, JavaScript. Form validation. Server-side technologies: Basic PHP. Server-side data validation. Database access with PDO» Transactions.» Exception handling. Introduction to Software Engineering and Information Systems 8 Lab sessions Each theory group will split into three lab groups: Two groups will go to labs. The third group will stay in the classroom with their laptops. Introduction to Software Engineering and Information Systems 9 IISSI 5

6 9/22/2013 Course project All along the course, a project worked out in groups must be developed: Web application with database access. Each group will have a tutor teacher. There will be two main deliveries, one in each semester. The tools proposed for project management and version control must be used. Introduction to Software Engineering and Information Systems 10 Tools for labs and project All tools can be either used in the cloud or can be installed on the student s laptop computer. Modules I & II projetsii (project management) Subversion (version control) Signavio (BPMN and UML) Oracle / Oracle Express (commercial DBMS) Oracle SQL Developer (DBMS administration) Introduction to Software Engineering and Information Systems 11 IISSI 6

7 9/22/2013 Tools for labs and project All tools can be either used in the cloud or can be installed on the student s laptop computer. Module III Apache HTTP Server + PHP (web server) Firefox + plugins (web client) WebDeveloper Firebug Any source code editor Aptana Notepad++ Eclipse... Introduction to Software Engineering and Information Systems 12 Per-course evaluation Two partial evaluations Each partial evaluation, two parts: Test exam (Blackboard): 60% Project defense: 40% 5 passed partial IISSI 50% if 5 50% if 5 1P 2P 60% 40% 60% 40% Test Project Test Project Introduction to Software Engineering and Information Systems 13 IISSI 7

8 9/22/2013 Per-course evaluation If the two partials are passed... Course is passed Final grade = (1 st partial + 2 nd partial) / 2 Introduction to Software Engineering and Information Systems 14 Per-course evaluation If some partial is failed... Course is failed Final grade = min(1 st partial, 2 nd partial) Passed partials and parts are saved for September and December Nothing is saved for next year. Introduction to Software Engineering and Information Systems 15 IISSI 8

9 9/22/2013 Ordinary evaluation June call Same criteria as per course. Grades obtained during course are still considered. Parts failed during course can be retrieved. Passed partial and parts are saved for September and December. Introduction to Software Engineering and Information Systems 16 Ordinary evaluation Sept. & Dec. calls Same criteria as per course. Only partials and parts passed in previous calls are saved. In each official call, the four parts (2 tests + 2 defenses) can be performed. Introduction to Software Engineering and Information Systems 17 IISSI 9

10 9/22/2013 Ordinary evaluation Sept. & Dec. calls Students must sit for all failed parts (tests and/or defenses) of failed partials in previous calls. Not sitting for a failed part of a failed partial implies a 0 (zero). Sitting for a passed part implies renunciation of the previously obtained grade. Introduction to Software Engineering and Information Systems 18 IISSI 10