Enter Title

email: tarmo.veskioja@ttu.ee

My skype username is: tarmove2

 The labs are on Fridays at 10.00.

Official consultation times are on Thursdays at 19.15-20.15 and on Fridays at 10.30-11.30 in room ITC-403 or in my own room ITC-622 (room telephone nr. 58843866).

Software

Rational RequisitePro  installation files can be copied from me, or accessed from the zaurus.ttu.ee server, be sure to register as a local server user.

Rational RequisitePro installation steps are given here. Additional steps are on this IBM web page.

The newest RequisitePro version is 7.1.4, it does not (yet) support MS Office 2013, only Office 2010 and earlier.

NB. RequisitePro 7.1.1.5 and higher 7.1.1.x and 7.1.2 and higher 7.1.2.x (one student reported that 7.1.2.4 was working) should support 64-bit Word. You should be able to choose the newer version during the installation from within the Installation Manager.
Or, it is also possible to download the 7.1.2.4 fixpack if you have 7.1.2 already installed (Fixpack is here).

 

The alternative software for managing requirements in this course is Rational Requirements Composer (separate product or in a Jazz sandbox). Further details on how to use it within the web browser will be given on week 2.

Materials

There is a preliminary metaproject, to describe the contents and process steps of the student project. For viewing just the process steps, look under the subfolder /Rose_model_in_html/FrontPage.html. Look under the Use Case view, Making a project, State / Activity model2, Making a project.

The main document of any RequisitePro project is the Vision document.

The Vision document of the metaproject also has additional information in the Table of Contents.

 A preliminary graph of requirements items in the metaproject is given here (note that students do not have to produce such a graph diagram for their own project).

 

Students are required to compose a requirements analysis project. The scope of the analysis stems from one business process per one student. The basic requirements of the project have not changed from previous years.

 A short description of the student project.

Necessary requirements views within the student project.

An example student project using Rational RequisitePro (password: Riivo). A preliminary graph of requirements items in Riivo's project is given here (generated by Tarmo, not a mandatory part of a student project).

Another example student project without using any requirements management software (password: Chris).

 

Lab 2.

Choosing the scope of your analysis and requirements engineering. The scope for one student is derived from one business process within a chosen organisation.

 Tying organisational vision with the analysed process (an example).

Describing the chosen business process with a UML activity diagram. A generic business process as an example.

A task for week 3:

mandatory part of the task: choose the organisation and the business process to be analysed. Describe it using this example. Before Lab 3 send it to my email.

Optional part of the task: draw a draft activity diagram and a draft domain model on a piece of paper (or using a UML case tool or some other drawing software). Take it with you for Lab 3.

 

Lab 3.

Open discussion of chosen business processes, activity and domain models.

A class task to define and choose different classification types for different goals.

ID card issuing process:

Goals vs. domain properties
hard vs. soft goals (based on how to measure)
functional goals vs. non-functional goals
system goals vs. software goals

Vision goals, organisationsl goals, process goals

 ------------------------------------------------

 Lab 4.

1. Open IBM Rational RequisitePro and take a 'Quick tour'  from under the Help menu (if you have not done it already).

2. Create a new folder under C:\temp\ for a new RequisitePro project.

Create a new RequisitePro project using a USE CASE template. Choose the previously created folder as the destination. The project name becomes a new subfolder.

3. Add new requirement types to your project for 'enterprise goals' (for vision and organisational goals) and 'process goals' (File - Project Administration - Properties, Requirement Types, Add).

4. Open the Vision document from within your own RequisitePro project. You can also open the Vision document of the Metaproject, but open that directly, not from within RequisitePro (ReqPro only opens one project at a time).

Copy your project description under paragaphs 1 and 2 (start with vision, organisational and process goals).

5. Select a goal definiton as a selected text block and define it as a new requirement using the RequisitePro menu (RequisitePro - Requirement - New) under Addins menu. Add other goals from your project description. Add connections (traces) between goals on the requirement properties dialog box either from under the Hierarchy or Traceability tabs.

6. At the end of the class pack the project folder and save it to your memory stick or to your H:\ drive. During next classes unpack it again under C:\temp\.

Trace enables to connect two different  types of requirements. Look at this doc for further description.

 

 ------------------------------------------------

Lab 5.

The steps (2-4) in Lab 4 are mandatory for the task (deadline) by week 6. However, you don't necessarily have to send the ReqPro project to me by email, you can show it to me in class.

 ------------------------------------------------

Lab 6.

Define stakeholder needs, add connections to other items. Define necessary views.

 ------------------------------------------------

Lab 8.

Start to define functional requirements and system features. Define functional requirements using the default USE CASE document template, create a new USE CASE document for each functional requirement (it is advisable to create a separate folder within RequisitePro as well).

See FURPS requirement types for additional info on requirement types.

See the metaproject for information on procedural steps.

Functional requirements have to be done (as a draft version) by week 10.

------------------------------------------------

On Nov.8th, I am away with bachelor students. If necessary, Enn will open the classroom at 12:00. The 16:00 practice will not take place.

------------------------------------------------

Other future deadlines are given here.

------------------------------------------------

Official project defending times in January 2014 are:

Monday January, 6th at 17-18, room ITC-627.
Friday January 10th at 15-16, room ITC-627.

If these official times do not suit you, then contact me via email.