IISSI Presentation

Transcription

1 9/23/ Software Engineering and Databases Group Department of Computer Languages and Systems University of Seville September 2014 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. September 2014 Introduction to Software Engineering and Information Systems 1 IISSI 1

2 9/23/2014 Course learning objectives (II) When passed, the student should be able to: Gather information about a not previously known problem domain, mainly through interviews and meetings. Develop a glossary of terms. Model simple business processes. Develop simple requirements proposals. Develop simple conceptual models from requirements. September 2014 Introduction to Software Engineering and Information Systems 2 Course learning 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. September 2014 Introduction to Software Engineering and Information Systems 3 IISSI 2

3 9/23/2014 Course learning objectives (IV) When passed, the student should be able to: Develop simple, adaptive 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. September 2014 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. September 2014 Introduction to Software Engineering and Information Systems 5 IISSI 3

4 9/23/2014 Module I: Introduction to SE & IS Introduction to Information Systems Information systems basics. Types of information systems. Business process modeling. Information systems requirements. September 2014 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: RA, 3NF. CM RM transformation SQL: DDL, DML, queries. Transactions. Query optimization. September 2014 Introduction to Software Engineering and Information Systems 7 IISSI 4

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

6 9/23/2014 Course project All along the course, two projects worked out in groups must be developed: 1. Requirements, analysis, design, and implementation of a relational database. 2. Web application with access to the database developed in the former project. The second project must be based on the first project. Each group will have a tutor teacher. September 2014 Introduction to Software Engineering and Information Systems 10 Course project There will be two main deliveries, one in each semester. The tools proposed for project management and version control must be used. September 2014 Introduction to Software Engineering and Information Systems 11 IISSI 6

7 9/23/2014 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) September 2014 Introduction to Software Engineering and Information Systems 12 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... September 2014 Introduction to Software Engineering and Information Systems 13 IISSI 7

8 9/23/2014 Per-course evaluation Two partial evaluations Each partial evaluation, two parts: Theory exam: 60% Passed project: 40% 5 passed partial IISSI 50% if 5 50% if 5 1P 2P 60% 40% 60% 40% Theory Passed project Theory Passed project September 2014 Introduction to Software Engineering and Information Systems 14 Per-course evaluation While the semester project is not passed the semester partial is not either, regardless of the theory grade September 2014 Introduction to Software Engineering and Information Systems 15 IISSI 8

9 9/23/2014 Per-course evaluation If the two partials are passed (together with their corresponding projects)... Course is passed Final grade = (1 st partial + 2 nd partial) / 2 September 2014 Introduction to Software Engineering and Information Systems 16 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. September 2014 Introduction to Software Engineering and Information Systems 17 IISSI 9

10 9/23/2014 Ordinary evaluation June call Same criteria as per course. Grades obtained during course are still considered. Parts failed during course can be remediated. Passed partial and parts are saved for September and December. September 2014 Introduction to Software Engineering and Information Systems 18 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 theories + 2 projects) can be performed. September 2014 Introduction to Software Engineering and Information Systems 19 IISSI 10

11 9/23/2014 Ordinary evaluation Sept. & Dec. calls Students must sit for all failed parts (theories and/or projects) 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 the renunciation of the previously obtained grade. September 2014 Introduction to Software Engineering and Information Systems 20 IISSI 11