Olet täällä

Information System Development Project

Information System Development Project
  • Code:  SYS1TF080
  • Extent:  12 cr (324 h)
  • Timing: 4th semester
  • Language:  English
  • Level:  Core studies
  • Type:  Compulsory

Starting level and linkage with other courses

Student has passed all compulsory courses on semesters 1-3 or can show and prove equivalent knowledge and skills.

Learning outcomes

Upon successful completion of the course, the student:

  • is able to act in a business oriented information system development project practicing disciplined and professional project method: according to the project plan, monitoring and estimating the project process, progress and quality
  • has gained the knowledge and understanding of a business oriented system development process lifecycle
  • is able to do analysis and design and to use prototyping methods and techniques
  • has basic knowledge of the use of a CASE tool in a system development process.

Course contents

Course focuses on a well-disciplined project of a model driven software development process of a business information system. The study project is based on a pre-defined business case and functional requirements analysis and covers definition, design and prototyping. Quality assurance – reviews, test planning and prototype based testing – is included into the project. UML and CASE-tool will be used in modeling, SQL Server Management Studio in design and implement of the database, and Visual Studio in application prototype development. It is essential that students have previously learned skills and knowledge of analysis and design methods, techniques, and implementation tools. The use of CASE-tool will be advised during the course.

Business driven systems development process and business case analysis

  • Development programs and projects
  • Development process lifecycle
  • Functional requirements of business case system

Project management

  • Project planning
  • Project communication & reporting
  • Project administration
  • Project implementation, management and steering

Software Requirements Analysis

  • Transition from business requirements to system analysis
  • Object Oriented Analysis
  • Process, tasks, and deliverables
  • Quality control: reviews and testing
  • Usability
  • UML and a CASE tool in OOA

Software Design

  • Transition from analysis to design
  • Process, tasks, and deliverables
  • Quality control: reviews and testing
  • Software test-planning
  • Database design and implementation
  • User interface design
  • Business layer design

Prototyping and testing

  • Transition from design to prototyping
  • Process, tasks, and deliverables
  • Implementing the prototype
  • Testing the system with prototype

International dimension

Methods, examples and ways of working apply approved and widely used international standards and disciplines of the global ICT and business community.

Teaching and learning methods

During the course students complete a small system project. Learning is based on class tuition; guided project based learning and individual project assignments. The complete amount of work is 20 hours per student per week.
The assessment of one’s own learning 1 h

Accreditation of prior learning (APL)

To get a passing (P) grade and exemption from the course, student must display and demonstrate the competence by certificates from earlier studies or work experience covering the course objectives and contents. It is possible to participate in the competence demonstration only once before taking the course.

Teachers responsible

Tuomo Ryynänen, Pasila

Juha Pispa, Pasila

Pekka Kamaja, Pasila

Ralf Rehn, Pasila

Course materials

  • Booch, G., Rumbaugh, J. & Jacobson, I. 1998. The Unified Modelling Language User Guide.
  • ISO / IEC 12207. Information Technology Software Lifecycle Processes.
  • Jacobson, I., Booch, G. & Rumbaugh, J. 1999. The Unified Software Development Process.
  • Perry, W. 1995. Effective Methods for Software Testing.
  • Rumbaugh, J., Jacobson, I. & Booch, G. 1999 Unified Modelling Language Reference Manual.
  • Quatrani, T. 1999. visual Modelling with Rational Rose and UML.
  • Handouts and course Web pages.
  • Krug, Steve (2006) Don't make me think, Second edition, New Riders Publishing
  • Rubin, Jeffrey & Chisnell, Dana (2008) Handbook of Usability Testing, Second Edition, Wiley Publishing, Inc.
  • Patton, Ron (2006) Software Testing, Second Edition, Sams Publishing
  • Shoemaker, Martin L., 2004, UML Applied, a .NET Perspective.

Modes of assessment

The assessment is based on the contribution to the project team and the team’s performance.

The assessment of one’s own learning does not influence the grade. The assignment is the same for all courses/modules and the answers will also be used for course/module development. The assignment is completed online in WinhaOpaali.