Teaching-CSC4521 for Dr J. Paul Gibson, INFormatique (INF), Telecom SudParis, France.

Overview

This site contains material for the module Génie logiciel pour la conception d'un Système d'Information (CSC4521), as part of the programme VAP DSI (Voie d'Approfondissement Intégration et Déploiement de Systèmes d’Information) It is complementary to the module Projet Système d'Information : réalisation et déploiement (CSC4522)

Sessions are scheduled for 3 hours. However, most sessions will be split into 3 parts, and the presentation/teaching part will usually take between 30 minutes and 60 minutes -

• I. Feedback from work completed since previous session
• II. Presentation of new material
• III. Practical work (in teams) with help from Paul

Evaluation

Your evaluation will be based on 4 aspects of your work:

• Requirements Model and Functional Architecture - deliverable 1 - Team mark (30%)
• Physical Architecture and its coherency with the requirements - deliverable 2 - Team mark (30%)
• Review of process of architecture design - Individual mark (20%)
• Engineering log/journal -Individual mark (20%)

The deadline for submitting your work is Monday 30th June. Please send your individual work by email (with the course code in the subject field). Please put your name at the top of each file submitted. I will acknoweldge reception of your email sublission and that I can open/read your files. If you do not recieve an acknowlegement by Tuesday 1st July then you must contact me (put URGENT in the email subject field).

Useful Links - (Software) Engineering Logs

Update your logs regularly (evey time you work On the project/module) with precise details of what you were doing/thinking. (A typical log entry for 1-3 hours of work would be 2-3 paragraphs.)
• It’s a naughty engineer who neglects his/her logbook, Clive (Max) Maxfield.
• A Work Log Template for Software Engineers, Gergely Orosz.
• Software Engineers should keep lab notebooks, Nelson Elhage, Made of Bugs.
• Note-Taking for Software Engineers -The importance of organizing your thoughts and efficiently keep them from haunting you, Eduardo Vedes.

Session 1: Wednesday 30th April (9h-12h30) B313

1.1 Introduction

• Introduction

Useful Links - (Software) Engineering Logs

• Système Informatique ou Système d’Information ?, Yves Grandmontagne.

1.2 Design Patterns

• Design Patterns

1.3 Singleton

• Singleton Design Pattern
• Singleton Code Archive

1.4 MVC

• MVC Design Pattern
• MVC Code Archive

1.5 Proxy

• Proxy Design Pattern
• Proxy Code Archive

Useful reading material

Useful external links

Session 2: Wednesday 30th April (14h-17h30) B313

2.1 Threads and processes for distributed system modeling and simulation

• An introduction to threads (in Java)
• Threads Code Archive

2.2 Distributed versus Centralised

• Comparing distributed and centralised architectures
• DistributedVersusCentralised Code Archive

Session 3: Wednesday 7th May (9h-12h30) B313

3.1 Iterator

You can try to work on this *before* the session.

• Iterator Design Pattern
• Iterator Code Archive

3.2 Software Reliability

• Software Reliability

Session 4: Wednesday 7th May (14h-17h30) B313

4.1 Faulty Stacks and Queues

You should complete as many of these problems as you can, before the next session.

• Fault tolerance - stacks and queues
• Faulty Stacks and Queues: Java Code Archive

Session 5: Wednesday 21st May (9h-12h30) B313

5.1 Functional Requirements

• Requirements Modelling
Problem: Working in teams (or alone) specify the requirements of a lift/elevator system:
• say what not how
• identify and formalise the clients' and users' vocabulary
• how easy is it to validate your specification?
• how easy is it to verify a design/implementation against your specification?

Additional reading material

• Requirements engineering in the year 00: A research perspective, A van Lamsweerde, 2000
• pdf
• Requirements Engineering: A Roadmap, Bashar Nuseibeh and Steve Easterbrook, 2000
• pdf
• On Non-Functional Requirements in Software Engineering, Lawrence Chung and Julio Cesar Sampaio do Prado Leite, 2009
• pdf
• Use cases - yesterday, today, and tomorrow, Ivar Jacobson, 2004
• pdf
• Structuring Use Cases with Goals, Alistair Cockburn, 1997
• pdf
• Writing effective use cases. Vol. 1, Alistair Cockburn, 2000
• pdf

Session 6: Wednesday 21st May (14h-17h30) B313

6.1 Lift Functional Design

• From requirements to design
• pdf

Problem -Transform an agreed specificaton of lift requirements into a functional design and verify that it is functionally correct.

Additional reading material

• On the Criteria To Be Used in Decomposing Systems into Modules, Parnas, 1972
• pdf
• A Rational Design Process: How and Why to Fake It, Parnas and Clements, 1986
• pdf
• A field study of the software design process for large systems, Curtis, B. and Krasner, H. and Iscoe, N.,1988
• pdf
• What is Software Design?, Jack W. Reeves, 1992
• pdf
• The risks of stopping too soon, Parnas, 2011
• pdf

Useful external links

• What does a Functional Design have to offer?, ITpedia.
• WHAT IS A FUNCTIONAL DESIGN SPECIFICATION (FDS)?, RealPars.
• What is a Functional Specification Document?, Essential Designs.

Wavestone visit: Thursday 22nd May (9h-12h30) B313

Sessions 7-8: Wednesday 28th May (9h-12h30, 14h-17h30) B313

7-8.1 Wavestone Project Functional Architecture

Today you will start working on the functional architecture of your project for Wavestone. You will need to identify the main use cases, and the data/functions that they depend on. Then map these on to the standard IoT design structure that Wavestone provided in their presentation. You should use UML diagrams, where appropriate, for modelling different aspects of your architectutre. Paul will help each team to make the 'best' decisions regarding the functional architecture of their specific project.

Session 9: Wednesday 4th June (9h-12h30) B313

9.1 Wavestone Project Functional Architecture Verification/Analysis

We must consider whether your functional architecture is 'good'. By what criteria do we judge a functional architecture. Which are general to all projects? Which are specific to each project? Paul will walk through an analysis with each team.

Each team will have 8-12 minutes to present:

• Functional requirements
• Functional architecture

There will be 10 minutes of questions/comments:

• Coherency between architecture and requirements
• Clarity and level of abstraction of architecture description
• Completeness of architecture description

The order of presentation will be:
• Cowpilot
• Mini-Serre
• Eezy Beezy
• Fourrage
• Cow care
• Bracelet

Session 10: Wednesday 4th June (14h-17h30) B313

10.1 Wavestone Project Architecture Analysis

• Architecture Analysis
• pdf

10.2 IoT Platforms

• IoT Platforms
• pdf

Wavestone visit: Thursday 5th June (14h-17h30) B313

Session 11: Thursday 12th June (9h-12h30) B313

11.1 Wavestone Project Tasks to complete

• What sort of intelligence do you really need?
• Based on your choice of IoT platform, what software needs to be devloped?
• A dashboard design and ethical issues related

Sessions 12 and 13: Wednesday 18th June (9h-12h30) (14h-17h30) B313

IoT Simulation - Sand Battery

Paul will review an IoT project concerned with the development of sand batteries (in Sweden). You are to write a dashboard that is connected to the battery via an IoT platfrom and gateway. You are also to write an intelligent controller inside the gateway, so that the system is guaranteed to be safe. You may choose to do the same work for your own project instead. Any work that follows the IoT architecture and provides a working dashboard will result in a 10% bonus to your final marks. So, eg, if you have 15 and you get the bonus, your final mark will be 16.5.

• IoTArchitectureSimulation Code Archive

Wavestone visit: Thursday 19th June (9h-12h30) B313