Requirements Engineering Document

download Requirements Engineering Document

of 52

Transcript of Requirements Engineering Document

  • 7/27/2019 Requirements Engineering Document

    1/52

    Software Engineering I Requirements Engineering Document

    1 FALL 2012

    School of Science and Engineering

    CSC 3324 - Software Engineering I

    Fall 2012

    Mohamed Ennahdi El Idrissi

    Amine Bellamkaddem

    Salah Zouiri

    Requirements Engineering Document

  • 7/27/2019 Requirements Engineering Document

    2/52

  • 7/27/2019 Requirements Engineering Document

    3/52

    Software Engineering I Requirements Engineering Document

    3 FALL 2012

    Another related question that we asked:

    Do we need to give the ANEB's users the possibility to create new users/accounts?

    The answer was:

    No, we want the same system that we already have in our web site. The client clicks on the

    link Create account, fill out a form, and then an administrator of the web site validates therequest. Similarly, we want to have another link in our web site that will point to the

    software that you will develop, and there, the client can fill out a form to create an account.

    Of course, ANEB should validate all requests of this kind.

    This discussion was of paramount important because we could gather several useful

    information. Here are the main requirements that we could gather:

    - The software needs to be a web-based solution;- The customer user has the possible actions:

    Provides data of the previous month for their organism only;

    Can view the general report which involves all organisms;

    Can also view the information of other organisms of the current and previous

    months (read-only access).

    - Every month, the customer is compelled to provide information about the previous

    month's activity related to their organism;

    - It's preferable to grant a deadline for users to submit their data. And Mr. Zniber

    suggests that the deadline is the 10th of each month;- The user can enter data several times, but they can disseminate the data only once

    (finalize/validate);

    - Beyond the tenth, if the customer doesn't validate the data, he will receive an alert

    (e-mail) to notify them that they are granted five more days as an additional chance

    to submit the data;

    - After validating data, the organism should not be able to modify it; however, ANEB

    consents itself to modify data at will;

    - The only possible action for the witness user is to visualize reports of all organisms.

    About reports, we could gather the following information:

    - ANEB needs three types of intervals:

    Annual

    quarterly

    Monthly

    - Reports present information by rubric, that is, for a determined rubric, a table of data

    of sub-rubrics (columns) and organism (rows). Their intersection allows displaying the

    value of a sub-rubric of an organism.

    - Below a sample general report of the so called rubric DONNES GNRALES:

  • 7/27/2019 Requirements Engineering Document

    4/52

    Software Engineering I Requirements Engineering Document

    4 FALL 2012

    Nombre

    d'leveurs

    individuels

    Nombre de

    coopratives

    Nbr

    d'leveurs

    adhrents au

    coopratives

    Nbr de

    CCL

    privs

    Nbr

    d'leveurs

    membres

    des CCL

    privs

    Nombre

    total

    d'leveurs

    CEBG 40 50 0 54 0 40

    Mabrouka 0 0 0 0 0 0

    Sakia_Al_Hamra 36 2 36 0 0 72

    Moulouya 3 15 1117 2 2 1122

    Zalagh 0 0 0 0 0 0

    Assoulala 50 0 0 0 0 50

    Nasr 0 0 0 0 0 0

    Colainord 1827 63 16000 80 2000 19827

    ACEB 0 81 0 0 0 0

    AET 6 94 13250 0 0 13256Tissir 24 1 24 0 0 48

    UMDCAL 0 27 4500 0 0 4500

    SAGB 68 69 12432 0 0 12500

    Oulad_Ghanem 0 0 0 0 0 0

    Bouhmame 0 0 0 0 0 0

    Total 2054 402 47359 136 2002 51415

    Moreover, Mr. Zniber wants to have a tool, which allows him to view the recorded data in

    screens (crans). Here, we have the following questionWhat do you mean by screen (cran)?

    Mr. Zniber, informed us that ANEB already has a web site, which is hosted by a provider

    called Hedoma, and he confirmed that we can use the same web server for hosting the

    new software because there is enough space in this server, and he doesn't need extra

    expenses for a new web server.

  • 7/27/2019 Requirements Engineering Document

    5/52

    Software Engineering I Requirements Engineering Document

    5 FALL 2012

    Draft n 1

    Our first meeting with Mr. Zniber was of a crucial importance. It allowed us to have a first list

    of requirements in addition to a list of questions, which we asked during the second

    meeting.

    The main modules deduced from the first elicitation round are:

    Manage Organisms

    Manage Users

    ANEB Users

    Organism Users

    Witness Users (Read Only)

    Manage Activities

    Manage Reports

  • 7/27/2019 Requirements Engineering Document

    6/52

    Software Engineering I Requirements Engineering Document

    6 FALL 2012

    Iteration No.2

    After adopting a breadth-first strategy during the first round, we came up with the following

    questions for Mr. Zniber:

    We have tried to retrieve the exact constituents of the structure in a clear way, because thedocument you did provide us with has some rubrics that are obvious, whereas others are confusing.

    We prepared this document which presents the hierarchy in a linear way to make sure we are getting

    along (see appendix B). Is the structure in the document valid?

    Structure desOrganismes Grs pa

    Yes, the structure is correct.

    When creating an organism, we are wondering about which information an ANEB User should

    provide about each organism?

    The entitlement, the description, the address, and the city of the organism.

    Since each organism's data are going to be provided by users belonging to their respective organism,

    do you want that a user be created whenever a new organism is created?

    For the time being, each organism has one and only one user. Hence, a user shall be created at the

    creation of a new organism.

    When creating a user for an organism, what is the information that you need to specify about each

    user?

    The first name, the last name, the profile (cadre, technicien, insminateur) of the user, and his/her

    e-mail.

    How do you handle the reports?

    I need to be able to choose which rubric level I want to display. I can choose a sub-rubric as the root

    of the report, and hence, I'll display values of all its infra-rubrics.

    Another example: I choose a rubric; I display values of all its sub-rubrics.

    I hope it is possible to present the data in a versatile manner (numeric data, curves, diagrams and

    pie-charts).

  • 7/27/2019 Requirements Engineering Document

    7/52

    Software Engineering I Requirements Engineering Document

    7 FALL 2012

    Draft No.2

    1. ANEB needs to manage organisms they are dealing with.

    1 leads to the following requirements :

    Each organism is identified with the following elements:

    Entitlement (intitul)

    Description

    Address

    City

    The functions needed for organisms management are : modifying,

    deleting, and viewing the list of organisms

    The list should allow ANEB users to have the important information about

    organisms as well as a search engine to search for a specific organism.

    2. A user management module with three types of users. ANEB will be in charge of

    creating all accounts.

    2 becomes:

    ANEB needs three types of users

    ANEBs user: will have the administrator role. They are created by

    ANEB personnel. Those users have full access (read-write)

    Users (organisms): For the time being, there'll be only one user

    per organism. The creation and assignation of the user will occur

    at the creation of a new organism.

    Organism users will be characterized by the following

    information:

    o First Name

    o Last Name

    o Profile

    Cadre

    Technicien

    Insminateur

    o a valid email address

    ANEB will create Witness users and will notify the involved

    elements in this operation via email.

    3. An activity management to manage the different interactions between users and

    organisms (data)

    3 leads to:

    Each month, users of type organisms are given 10 days to enter

    information of the previous month concerning their organisms.

  • 7/27/2019 Requirements Engineering Document

    8/52

    Software Engineering I Requirements Engineering Document

    8 FALL 2012

    Beyond the tenth, if the user doesn't validate the data, he will receive a

    reminder (e-mail) to notify them that they are granted five more days as

    an extra chance to submit the data

    Once the data is validated, organism users should not be able to modify it;

    however, ANEB consents itself to modify data at will

    4. ANEB needs a report management to display information about different organisms

    in the same view in order to be able the compare them.

    4 becomes:

    Graphical representation of statistical data (numeric data, curves,

    diagrams and pie charts)

    Each report is customizable:

    e.g. a rubric and all its sub-rubrics, including/excluding the latter's

    infra-rubrics

    generate a report for an sub-rubric and its infra-rubrics only

    ...

    The possibility to display reports in annual, trimestrial, or monthly basis

  • 7/27/2019 Requirements Engineering Document

    9/52

    Software Engineering I Requirements Engineering Document

    9 FALL 2012

    Stable Release

    Section A: Functional Requirements

    1. Function Manage Organisms

    1.1 Sub Function Create Organism, which includes the creation of an organism user as well;

    1.2 Sub Function Modify Organism;

    1.3 Sub Function View all Organisms;

    1.4 Sub Function Search Organisms

    by Entitlement

    by City;

    1.5 Sub Function View An Organism

    Navigate its Hierarchy with values

    Create hierarchy element with value

    Modify hierarchy element with value

    Delete hierarchy element with value.

    2. Function Manage Users

    2.1 Sub Function Create User

    ANEB User

    Organism User

    Witness User;

    2.2 Sub Function View all Users with their attributes;

    2.3 Sub Function View a user;

    2.4 Sub Function Modify User;

    2.5 Sub Function Delete User;2.6 Sub Function Search for User

    by name (first name and/or last)

    by type.

    3. Function Manage Activities

    3.1 Sub Function Manage monthly data form by ANEB Users

    Trigger new activity

    Remind organism contacts;

    3.2 Sub Function Navigate organism data by ANEB Users, Organism Users and Witness Users;

    3.3 Sub Function Modify organism data by ANEB Users;

    3.4 Sub Function Fill out and submit monthly data form by Organism Users;

    3.5 Sub Function Manage organisms data.

    4. Function Manage Reports

    4.1 Sub Function Generate report after selecting a root among the hierarchy (rubric, sub-

    rubric...), the period, the year (when the period is yearly), the trimester or the month. This sub

    function involves also the type of the graphics to use.

  • 7/27/2019 Requirements Engineering Document

    10/52

    Software Engineering I Requirements Engineering Document

    10 FALL 2012

    Section B: Non Functional Requirements

    1. Software should be remotely accessible;

    2. Should be compatible with Microsoft IE, Mozilla Firefox, and Google Chrome;

    3. At least the graphical user interface should be in French.

  • 7/27/2019 Requirements Engineering Document

    11/52

    Software Engineering I Requirements Engineering Document

    11 FALL 2012

    Appendix A (Sample example of the hierarchy contained in the excel file)

    I. Donnes gnralesadhrents actuels

    Nombre d'leveurs individuels 40

    Nombre de coopratives 50

    Nombre d'lveurs

    Nombre de CCL privs 54

    Nombre d'lveurs

    Nombre total d'leveurs

    II. Programme dinsmination artificielle

    Nombre de circuits IA :

    9

    Nombre de vhicules IA :

    10

    Nombre dinsminateurs :

    10

    Mise la disposition 6

    Recruts 4

    Ralisations en insmination artificielle:o Ralisations globales

    IA1 Race pure IA1 - Race

    croise

    IA1 - Race

    locale

    Rptitions

    Totales

    IA totales Nbr total

    desleveurs

    touchs

    26692

    Appendix B (the hierarchy in a linear way)

    Rubrique Donnes gnrales

    Sous-Rubrique Nombre d'leveurs individuels

    Sous-Rubrique Nombre de coopratives

    Infra-Rubrique Nombre d'leveurs

    Sous-Rubrique Nombre de CCL privs

    Infra-Rubrique Nombre d'leveurs

    Sous-Rubrique Nombre total d'leveurs

    Rubrique Programme dinsmination artificielle

    Sous-Rubrique Nombre de circuits IA :

    Sous-Rubrique Nombre de vhicules IA :

    Sous-Rubrique Nombre dinsminateurs :

    Infra-Rubrique Mis la DispositionInfra-Rubrique Recruts

  • 7/27/2019 Requirements Engineering Document

    12/52

    Software Engineering I Requirements Engineering Document

    12 FALL 2012

    Sous-Rubrique Ralisations en insmination artificielle:

    Infra-Rubrique Ralisations globales

    Sous-Infra-Rubrique IA1 Race pure

    Sous-Infra-Rubrique IA1 - Race croise

    Sous-Infra-Rubrique IA1 - Race locale

    Sous-Infra-Rubrique Rptitions Totales

    Sous-Infra-Rubrique IA totales

    Sous-Infra-Rubrique Nbr total des leveurs touchs

    Sous-Infra-Rubrique Contrle gestation

    Sous-Infra-Rubrique Contrle naissance

    Infra-Rubrique Dtail des IA1 par race pure

    Sous-Infra-Rubrique Holstein

    Sous-Infra-Rubrique Montbliarde

    Sous-Infra-Rubrique Charolais

    Sous-Infra-Rubrique BrahmanSous-Infra-Rubrique BBB

    Sous-Infra-Rubrique Limousin

    Sous-Infra-Rubrique Total

    Sous-Rubrique Utilisations des semences (anne 2010)

    Infra-Rubrique Semences CRIA locales

    Sous-Infra-Rubrique Holstein

    Sous-Infra-Rubrique Montbliarde

    Sous-Infra-Rubrique Charolais

    Sous-Infra-Rubrique Brahman

    Sous-Infra-Rubrique BBB

    Sous-Infra-Rubrique Autres

    Infra-Rubrique Semences importes

    Sous-Infra-Rubrique Holstein

    Sous-Infra-Rubrique Montbliarde

    Sous-Infra-Rubrique Charolais

    Sous-Infra-Rubrique Brahman

    Sous-Infra-Rubrique BBB

    Sous-Infra-Rubrique Autres

    Infra-Rubrique TotalSous-Infra-Rubrique Holstein

    Sous-Infra-Rubrique Montbliarde

    Sous-Infra-Rubrique Charolais

    Sous-Infra-Rubrique Brahman

    Sous-Infra-Rubrique BBB

    Sous-Infra-Rubrique Autres

    Rubrique Programme du contrle laitier

    Sous-Rubrique Nombre agents contrleurs laitiers:

    Sous-Rubrique Nombre vhicules utiliss :

    Sous-Rubrique Nombre dunits ppinires :

    Sous-Rubrique Nbr total dtables Contrles

  • 7/27/2019 Requirements Engineering Document

    13/52

    Software Engineering I Requirements Engineering Document

    13 FALL 2012

    Infra-Rubrique Holstein

    Infra-Rubrique Montbliarde

    Infra-Rubrique Total 35

    Sous-Rubrique Effectif total de vaches prsentes

    Infra-Rubrique Holstein

    Infra-Rubrique Montbliarde

    Infra-Rubrique Total 626

    Sous-Rubrique Effectif total de vaches contrles

    Infra-Rubrique Holstein

    Infra-Rubrique Montbliarde

    Infra-Rubrique Total 473

    Sous-Rubrique Nombre lactations termines

    Infra-Rubrique Holstein

    Infra-Rubrique Montbliarde

    Infra-Rubrique TotalSous-Rubrique Moyenne lait 305 jours-kg par lactation termine

    Infra-Rubrique Holstein

    Infra-Rubrique Montbliarde

    Infra-Rubrique Total

    Sous-Rubrique Moyenne matires grasse 305 jours-kg par lactation termine

    Infra-Rubrique Holstein

    Infra-Rubrique Montbliarde

    Infra-Rubrique Total

    Sous-Rubrique Nombre gnisses slectionnes

    Infra-Rubrique Holstein

    Infra-Rubrique Montbliarde

    Infra-Rubrique Total

    Rubrique Programme didentification gnralise des bovins (IGB)

    Sous-Rubrique Nombre agents identificateurs

    Infra-Rubrique Techniciens ONSSA :

    Infra-Rubrique Insminateurs :

    Infra-Rubrique Contrleurs laitiers :

    Infra-Rubrique Autres :

    Sous-Rubrique Nombre de vhicules nouvellement utilissInfra-Rubrique Vhicules OP

    Infra-Rubrique Vhicules ONSSA

    Infra-Rubrique Autres :

    Sous-Infra-Rubrique Nombre tables touches dans le mois

    Sous-Infra-Rubrique Nombre Bovins identifis dans le mois

    Sous-Infra-Rubrique Nombre CIAB tablis dans le mois

    Sous-Infra-Rubrique Cumul de Bovins identifis depuis le dbut de l'opratio

    Sous-Infra-Rubrique Anne dmarrage IGB

    Rubrique Programme de formation et information des leveurs et techniciens

    Sous-Rubrique Dsignation

    Infra-Rubrique A.A

  • 7/27/2019 Requirements Engineering Document

    14/52

    Software Engineering I Requirements Engineering Document

    14 FALL 2012

    Sous-Infra-Rubrique Nombre de session/thme

    Sous-Infra-Rubrique Nombre de bnficiaires :

    sous-Sous-Infra-Rubrique Eleveurs

    sous-Sous-Infra-Rubrique Techniciens

    Infra-Rubrique IA

    Sous-Infra-Rubrique Nombre de session/thme

    Sous-Infra-Rubrique Nombre de bnficiaires :

    Sous-Sous-Infra-Rubrique Eleveurs

    Sous-Sous-Infra-Rubrique Techniciens

    Infra-Rubrique IGB

    Sous-Infra-Rubrique Nombre de session/thme

    Sous-Infra-Rubrique Nombre de bnficiaires :

    Sous-Sous-Infra-Rubrique Eleveurs

    Sous-Sous-Infra-Rubrique Techniciens

    Infra-Rubrique CLSous-Infra-Rubrique Nombre de session/thme

    Sous-Infra-Rubrique Nombre de bnficiaires :

    Sous-Sous-Infra-Rubrique Eleveurs

    Sous-Sous-Infra-Rubrique Techniciens

    Infra-Rubrique Autres

    Sous-Infra-Rubrique Nombre de session/thme

    Sous-Infra-Rubrique Nombre de bnficiaires :

    Sous-Sous-Infra-Rubrique Eleveurs

    Sous-Sous-Infra-Rubrique Techniciens

    Infra-Rubrique Total

    Sous-Infra-Rubrique Nombre de session/thme

    Sous-Infra-Rubrique Nombre de bnficiaires :

    Sous-Sous-Infra-Rubrique Eleveurs

    Sous-Sous-Infra-Rubrique Techniciens

    Rubrique Contribution au programme de lutte contre les maladies contagieuses

    Sous-Rubrique Nbre de journes de sensibilisation

    Sous-Rubrique Nbr dleveurs bnficiaires

    Sous-Rubrique Nbr de cas de tuberculose et brucellose

    Sous-Rubrique Nbr de bovins abattusSous-Rubrique Nbr de bovins subventionns

    Rubrique Suivi technique des tables

    Sous-Rubrique Nombre dtables encadres et suivies sur le plan technique.

    Sous-Rubrique Nombre dtables encadres sur le plan sanitaire.

    Appendix C (Spider Network like hierarchy)

    ANEB.xml

  • 7/27/2019 Requirements Engineering Document

    15/52

    Software Engineering I Requirements Engineering Document

    15 FALL 2012

    Using the .xml file above, you can view the hierarchy in a form of a diagram using the

    following like:

    http://www.diagram.ly/

    File -> Open -> ANEB.xml

    http://www.diagram.ly/http://www.diagram.ly/http://www.diagram.ly/
  • 7/27/2019 Requirements Engineering Document

    16/52

    Software Engineering I Requirements Engineering Document

    16 FALL 2012

    School of Science and Engineering

    CSC 3324 - Software Engineering IFall 2012

    System Models

    Mohamed Ennahdi El Idrissi

    Amine BellamkaddemSalah Zouiri

    Due Date: November1st, 2012

  • 7/27/2019 Requirements Engineering Document

    17/52

    Software Engineering I Requirements Engineering Document

    17 FALL 2012

    Introduction

    In this deliverable, we used SilverRun CASE tool in order to produce the context diagram that

    has been formally described.

    The tool we took advantage of to represent the CD and CPMs is SilverRun CASE tool to

    generate all the CPMs related to your information system.

    We formally described each CPM of the system and Draw the conceptual architecture of your

    information system and describe it in a separate page;

    Our GUI will be sent by email. Its entry point is login.html, and it is a mere navigation.

  • 7/27/2019 Requirements Engineering Document

    18/52

    Software Engineering I Requirements Engineering Document

    18 FALL 2012

    Context Diagram

  • 7/27/2019 Requirements Engineering Document

    19/52

    Software Engineering I Requirements Engineering Document

    19 FALL 2012

    Description of the context diagram of ANEB's project

    The context diagram in figure 1 provides a high-level representation of the whole system to

    be managed by ANEB's users, organisms' users, and witnesses. This system contains four processes,

    which are: Manage Organisms, Manage Users, Manage Activities, and Manage Reports, threeexternal entities, which are: ANEB's users, Organisms' users, and Witnesses, and three data stores,

    which are: Organisms store, Users store, and Activities store.

    Here is the description of each process:

    Manage Organisms: The process Manage Organisms provides ANEB's Users the right to

    explore and exploit organisms. It allows the user to add, update, delete, search for an

    organism, view the description of all organisms with their attributes, and view the

    description of a specific organisms with the possibility of managing its hierarchy

    Manage Users: The process Manage Users consists of providing ANEB's users the right to

    manage the different users who interact with the system. it provides the possibility to add,modify user's attributes, delete, search for a user (by name and /or by type), view a

    description of a specific user, and view the description of all users with their attributes.

    Manage Activities: The process manages activities is responsible for managing the data

    provided by the different organisms. It allows ANEB's users to navigate, modify, and manage

    organisms data. It allows organisms' users to submit monthly data form and to navigateorganisms data, and it allows witnesses to navigate organisms data.

    Manage reports: The process Manage reports consists of providing ANEB's users, organismsusers and witnesses the right to visualize organisms numeric and graphical reports

  • 7/27/2019 Requirements Engineering Document

    20/52

  • 7/27/2019 Requirements Engineering Document

    21/52

    Software Engineering I Requirements Engineering Document

    21 FALL 2012

    CPM Manage Organisms

    The process Manage Organisms provides ANEB's users the right to explore and exploit the

    organisms different attributes.

    Explore Organisms: The process Explore Organisms allows the user to add new organisms,

    modify their attributes, delete an organism, view organisms information, and search for a

    specific organism. Those operations are done by accessing the organisms store.

    Exploit Organisms: The process Exploit Organisms consists of view a specific organism and

    exploit if.

    During the step of Analysis, we have realized the absence of the sub-function Delete an Organism

    that we added to the CPM Manage Organisms.

  • 7/27/2019 Requirements Engineering Document

    22/52

    Software Engineering I Requirements Engineering Document

    22 FALL 2012

    Explore organisms

  • 7/27/2019 Requirements Engineering Document

    23/52

    Software Engineering I Requirements Engineering Document

    23 FALL 2012

    CPM Explore Organisms

    The process Explore Organisms has four main sub-processes, which are: Create Organisms,

    Modify Organisms, View all Organisms, and Search for an Organism.

    Create Organisms: This sub-process allows the ANEB's users to add/create a new organism

    by entering its different attributes. The new organism is added to Organisms store

    Modify Organisms: Using this sub-process, the user will be able to modify organisms'

    attributes.

    Delete Organisms: This sub-process allows ANEBs users to delete an organism from theorganisms store.

    View all Organisms: This sub-process allows the user to visualize information about all

    organisms.

    Search for an Organism: This sub-process allows the user to search for a specific using some

    specific attributes, which are: search by entitlement and search by city.

  • 7/27/2019 Requirements Engineering Document

    24/52

    Software Engineering I Requirements Engineering Document

    24 FALL 2012

    Exploit organisms

  • 7/27/2019 Requirements Engineering Document

    25/52

    Software Engineering I Requirements Engineering Document

    25 FALL 2012

    CPM Exploit Organisms

    The process Exploit Organisms contains one main sub-process, which is: View an Organism.

    View an Organisms: This sub-process consists of providing ANEB's users the possibility to

    view organisms and manage their hierarchy elements with their values

  • 7/27/2019 Requirements Engineering Document

    26/52

    Software Engineering I Requirements Engineering Document

    26 FALL 2012

    View an organism

  • 7/27/2019 Requirements Engineering Document

    27/52

    Software Engineering I Requirements Engineering Document

    27 FALL 2012

    CPM View an Organism

    The process View an Organism has four sub-processes, which are: Navigate hierarchy with

    value, Create hierarchy with value, Modify hierarchy with value, and Delete hierarchy with value.

    Navigate hierarchy with value: this sub-process allows ANEB's users to navigate

    among all the elements of organisms' structure to check or consume the values.

    Create hierarchy with value: using this sub-process, ANEB's users will be able to add

    new rubrics, since the structure of organisms is subject to change.

    Modify hierarchy with value: this sub-process allows ANEB's users to alter the label

    and/or the data type of each rubric. Changing the parent-rubric/child-rubric is

    included in this module.

    Delete hierarchy with value: this sub-process allows ANEB's users to delete rubrics as

    soon as they become obsolete.

  • 7/27/2019 Requirements Engineering Document

    28/52

    Software Engineering I Requirements Engineering Document

    28 FALL 2012

    Manage Users

  • 7/27/2019 Requirements Engineering Document

    29/52

    Software Engineering I Requirements Engineering Document

    29 FALL 2012

    CPM Manage Users

    The process Manage Users allows ANEB's users to explore users' different attributes.

    Explore Users: The process Explore Users consists of providing ANEB's users the right to add

    new users, modify their attributes, delete a user, search for a user, view information about a

    specific user as well as view the description of all users. Those operations are done by acting

    on the users store.

  • 7/27/2019 Requirements Engineering Document

    30/52

    Software Engineering I Requirements Engineering Document

    30 FALL 2012

    Explore Users

  • 7/27/2019 Requirements Engineering Document

    31/52

    Software Engineering I Requirements Engineering Document

    31 FALL 2012

    CPM Explore Users

    The process Explore Users has four main sub-processes, which are: Create Users, View all Users,

    View a User, Modify User, Delete User, Search for User.

    Create User: Using this process, ANEB's users will be able to add a new user by entering its

    attributes. The new user is added to Users' store

    View all Users: This process provides the possibility to view information about all users

    View a Users: This process allows ANEB's user to view information about a specific user

    Modify User: This process consists of providing ANEB's users the right to modify users'

    attributes

    Delete User: The process Delete User allows ANEB's users to delete a user from users' store

    Search for User: Using this process, the user will be able to search for a specific user using

    some specific attributes

  • 7/27/2019 Requirements Engineering Document

    32/52

    Software Engineering I Requirements Engineering Document

    32 FALL 2012

    Manage Activities

  • 7/27/2019 Requirements Engineering Document

    33/52

    Software Engineering I Requirements Engineering Document

    33 FALL 2012

    CPM Manage Activities

    The process Manage Activities allows ANEB's users as well as organisms' users and witnesses to

    explore activities, which consists of the data provided by the different organism.

    Explore Activities: The process Explore Activities allows ANEB's users to manage monthly

    data, navigate organisms data, and modify organisms data, it allows organisms' users to

    submit monthly data and navigate organisms data, and it allows witnesses to navigate

    organisms data

  • 7/27/2019 Requirements Engineering Document

    34/52

    Software Engineering I Requirements Engineering Document

    34 FALL 2012

    Explore activities

  • 7/27/2019 Requirements Engineering Document

    35/52

  • 7/27/2019 Requirements Engineering Document

    36/52

    Software Engineering I Requirements Engineering Document

    36 FALL 2012

    Manage Reports

  • 7/27/2019 Requirements Engineering Document

    37/52

    Software Engineering I Requirements Engineering Document

    37 FALL 2012

    CPM Manage Reports

    The process Manage Reports allows ANEB's users as well as organisms' users and witnesses

    to explore reports.

    Explore Reports: The process Explore Reports consists of providing ANEBs users,

    organisms users, and witnesses the right to generate and visualize reports

  • 7/27/2019 Requirements Engineering Document

    38/52

    Software Engineering I Requirements Engineering Document

    38 FALL 2012

    Explore reports

  • 7/27/2019 Requirements Engineering Document

    39/52

    Software Engineering I Requirements Engineering Document

    39 FALL 2012

    CPM Explore Reports

    The process Explore Reports has two main sub-processes, which are: Generate numeric

    reports and Generate graphical reports.

    Generate numeric reports: Using this sub-process, ANEBs users, organisms users,

    and witnesses will be able to generate and visualize numeric reports about different

    organisms. The numeric reports will be displayed in a grid-like format.

    Generate graphical reports: This sub-process provides ANEBs users, organisms

    users, and witnesses the right to generate and visualize graphical reports about

    different organisms. The graphical reports consist mainly on graphs using colors,

    words, and numbers.

  • 7/27/2019 Requirements Engineering Document

    40/52

    Software Engineering I Requirements Engineering Document

    40 FALL 2012

    Functional Architecture

  • 7/27/2019 Requirements Engineering Document

    41/52

    Software Engineering I Requirements Engineering Document

    41 FALL 2012

    Dictionary: First Round

    Attributes Document Description I/D C/NCPossible

    anomalies

    Nom de lOrganisationProfessionnelle bilan_evaluation _canevas.docx The name of the organisation D NC Synonymy

    Adresse bilan_evaluation _canevas.docx The address of the organisation D NC

    Tlphone bilan_evaluation _canevas.docx The phone of the organisation D NC

    E-mail bilan_evaluation _canevas.docx The email of the organisation D NC Synonymy

    Fax bilan_evaluation _canevas.docx The fax of the organisation

    Nombre dleveursindividuels bilan_evaluation _canevas.docx

    Number of independent farmerswho operate for the concernedorganisms D NC

    Nombre de coopratives bilan_evaluation _canevas.docx

    number of cooperativesoperating for the processedorganism D NC

    Nombre dleveurs bilan_evaluation _canevas.docx Number of cooperative farmers D NC

    Nombre de CCL privs bilan_evaluation _canevas.docxNumber of dairy cooperatives(cooprative laitres) D NC

    Nombre dleveurs bilan_evaluation _canevas.docx Number of CCL farmers D NC

    Nombre total dleveurs bilan_evaluation _canevas.docx The total number of farmers D NC

    Nombre de circuits IA bilan_evaluation _canevas.docxNumber of Artificial InseminatorCircuits D NC

    Nombre de vhicules IA bilan_evaluation _canevas.docxNumber of Artificial inseminatorVehicules D NC

    Nombre dinsminateurs bilan_evaluation _canevas.docx Number of inseminators D NC

    Mis la disposition bilan_evaluation _canevas.docxNumber of availableinseminators D NC

    Recruts bilan_evaluation _canevas.docx Number of hired inseminators D NC

    IA1 Race pure bilan_evaluation _canevas.docx

    Number of artificial inseminator

    purebred D NC

    IA1 - Race croise bilan_evaluation _canevas.docxNumber of artificial inseminatorcrossbred D NC

    IA1 - Race locale bilan_evaluation _canevas.docxNumber of artificial inseminatorlocal breed D NC

    Rptitions Totales bilan_evaluation _canevas.docx Total of repetitions D C

    IA totales bilan_evaluation _canevas.docx Artificial Inseminator Totals D C

    Nbr total des leveurstouchs bilan_evaluation _canevas.docx Number of affected farmers D NC

    Contrle gestation bilan_evaluation _canevas.docx Gestation Control D NC

    Contrle naissance bilan_evaluation _canevas.docx Birth Control D NC

    Nombre bilan_evaluation _canevas.docx Number of Holsten D NC Homonymy

    Nombre bilan_evaluation _canevas.docx Number of Montbliarde D NC Homonymy

    Nombre bilan_evaluation _canevas.docx Number of Charolai D NC Homonymy

    Nombre bilan_evaluation _canevas.docx Number of Brahman D NC Homonymy

    Nombre bilan_evaluation _canevas.docx Number of BBB D NC Homonymy

    Nombre bilan_evaluation _canevas.docx Number of Other D NC Homonymy

    Nombre bilan_evaluation _canevas.docx Total of purebred D C Homonymy

    Holstein bilan_evaluation _canevas.docxSemences CRIA locales pourHolstein D NC Homonymy

    Holstein bilan_evaluation _canevas.docxSemences importes pourHolstein D NC Homonymy

    Holstein bilan_evaluation _canevas.docx Total Semence pour Holstein D C Homonymy

    Montbliarde bilan_evaluation _canevas.docxSemences CRIA locales pourMontbliarde D NC Homonymy

    Montbliarde bilan_evaluation _canevas.docx Semences importes pour D NC Homonymy

  • 7/27/2019 Requirements Engineering Document

    42/52

    Software Engineering I Requirements Engineering Document

    42 FALL 2012

    Montbliarde

    Montbliarde bilan_evaluation _canevas.docxTotal Semences pourMontbliarde D C Homonymy

    Charolais bilan_evaluation _canevas.docxSemences CRIA locales pourCharolais D NC Homonymy

    Charolais bilan_evaluation _canevas.docx

    Semences importes pour

    Charolais D NC HomonymyCharolais bilan_evaluation _canevas.docx Total Semences pour Charolais D C Homonymy

    Brahman bilan_evaluation _canevas.docxSemences CRIA locales pourCharolais D NC Homonymy

    Brahman bilan_evaluation _canevas.docxSemences importes pourBrahman D NC Homonymy

    Brahman bilan_evaluation _canevas.docx Total Semences pour Brahman D C Homonymy

    BBB bilan_evaluation _canevas.docxSemences CRIA locales pourBBB D NC Homonymy

    BBB bilan_evaluation _canevas.docx Semences importes pour BBB D NC Homonymy

    BBB bilan_evaluation _canevas.docx Total Semences pour BBB D C Homonymy

    Autres bilan_evaluation _canevas.docx

    Semences CRIA locales pour

    Autres D NC Homonymy

    Autres bilan_evaluation _canevas.docxSemences importes pour

    Autres D NC Homonymy

    Autres bilan_evaluation _canevas.docx Total Semences pour Autres D C Homonymy

    Total bilan_evaluation _canevas.docx Total Semences CRIA locales D C Homonymy

    Total bilan_evaluation _canevas.docx Total Semences importes ? D C Homonymy

    Total bilan_evaluation _canevas.docx Total Autres Semences D C Homonymy

    Nombre agents contrleurslaitiers bilan_evaluation _canevas.docx

    Number of agents dairycontrollers D NC

    Nombre vhicules utiliss bilan_evaluation _canevas.docx Number of used vehicles D NC

    Nombre dunitsppinires bilan_evaluation _canevas.docx Number of nurseries units D NC

    Holstein bilan_evaluation _canevas.docx Nbr total dtables Contrles D NC Homonymy

    Holstein bilan_evaluation _canevas.docxEffectif total de vachesprsentes D NC Homonymy

    Holstein bilan_evaluation _canevas.docxEffectif total de vachescontrles D NC Homonymy

    Holstein bilan_evaluation _canevas.docxNumber lactations terminesdans lanne D NC Homonymy

    Holstein bilan_evaluation _canevas.docxMoyenne lait 305 jours-kg parlactation termine dans lanne D NC Homonymy

    Holstein bilan_evaluation _canevas.docx

    Moyenne matires grasse 305jours-kg par lactation terminedans lanne D NC Homonymy

    Holstein bilan_evaluation _canevas.docx

    Number gnisses slectionnes

    dans lanne D NC Homonymy

    Montbliarde bilan_evaluation _canevas.docx Nbr total dtables Contrles D NC Homonymy

    Montbliarde bilan_evaluation _canevas.docxEffectif total de vachesprsentes D NC Homonymy

    Montbliarde bilan_evaluation _canevas.docxEffectif total de vachescontrles D NC Homonymy

    Montbliarde bilan_evaluation _canevas.docxNumber lactations terminesdans lanne D NC Homonymy

    Montbliarde bilan_evaluation _canevas.docxMoyenne lait 305 jours-kg parlactation termine dans lanne D NC Homonymy

    Montbliarde bilan_evaluation _canevas.docx

    Moyenne matires grasse 305jours-kg par lactation termine

    dans lanne D NC Homonymy

    Montbliarde bilan_evaluation _canevas.docxNombre gnisses slectionnesdans lanne D NC Homonymy

  • 7/27/2019 Requirements Engineering Document

    43/52

    Software Engineering I Requirements Engineering Document

    43 FALL 2012

    Total bilan_evaluation _canevas.docxTotal Nbrtotal dtablesContrles D NC Homonymy

    Total bilan_evaluation _canevas.docxTotal Effectif total de vachesprsentes D NC Homonymy

    Total bilan_evaluation _canevas.docxTotal Effectif total de vachescontrles D NC Homonymy

    Total bilan_evaluation _canevas.docxTotal Nombre lactationstermines dans lanne D NC Homonymy

    Total bilan_evaluation _canevas.docx

    Total Moyenne lait 305 jours-kgpar lactation termine danslanne D NC Homonymy

    Total bilan_evaluation _canevas.docx

    Total Moyenne matires grasse305 jours-kg par lactationtermine dans lanne D NC Homonymy

    Total bilan_evaluation _canevas.docxTotal Nombre gnissesslectionnes dans lanne D NC Homonymy

    Techniciens ONSSA bilan_evaluation _canevas.docxNumber agents identificateurs(du type Techniciens ONSSA) D NC

    Insminateurs bilan_evaluation _canevas.docx

    Number agents identificateurs

    (du type Insminateurs) D NC

    Contrleurs laitiers bilan_evaluation _canevas.docxNumber agents identificateurs(du type Contrleurs laitiers) D NC

    Autres bilan_evaluation _canevas.docxNumber agents identificateurs(du type Autres) D NC

    Vhicules OP bilan_evaluation _canevas.docxNumber of vhicules utiliss (dutype Vhicules OP) D NC

    Vhicules ONSSA bilan_evaluation _canevas.docxNumber of vhicules utiliss (dutype Vhicules ONSSA) D NC

    Autres bilan_evaluation _canevas.docxNumber of vhicules utiliss (dutype Autres) D NC

    Nombre tables touchesdans lanne bilan_evaluation _canevas.docx

    Number of stables affected inthe year D NC

    Nombre Bovins identifisdans lanne bilan_evaluation _canevas.docx

    Number of cattle identified inthe year D NC

    Nombre CIAB tablis danslanne bilan_evaluation _canevas.docx

    number of (CartedIdentification etdAccompagnement desBovins) established in the year D NC

    Cumul de Bovins identifisdepuis le dbut delopration bilan_evaluation _canevas.docx

    Accumulated Cattle identifiedsince the beginning of theoperation D NC

    Anne dmarrage IGB bilan_evaluation _canevas.docx('identification gnralise desbovins) year start D NC

    Nombre de session/thme bilan_evaluation _canevas.docx

    Training number of

    meetings/theme A.A D NC

    Nombre de session/thme bilan_evaluation _canevas.docxTraining number ofmeetings/theme I.A D NC

    Nombre de session/thme bilan_evaluation _canevas.docxTraining number ofmeetings/theme I.G.B D NC

    Nombre de session/thme bilan_evaluation _canevas.docxTraining number ofmeetings/theme C.l D NC

    Nombre de session/thme bilan_evaluation _canevas.docxTraining number ofmeetings/theme Autres D NC

    Nombre de session/thme bilan_evaluation _canevas.docxTraining number ofmeetings/theme Total D C

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx

    Number of beneficiaries(Eleveurs) A.A D NC

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx

    Number of beneficiaries(Eleveurs) I.A D NC

  • 7/27/2019 Requirements Engineering Document

    44/52

    Software Engineering I Requirements Engineering Document

    44 FALL 2012

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx

    Number of beneficiaries(Eleveurs) I.G.B D NC

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx

    Number of beneficiaries(Eleveurs) C.I D NC

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx

    Number of beneficiaries(Eleveurs) Autres D NC

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx

    Number of beneficiaries(Eleveurs) Total D C

    Nombre de bnficiairesTechniciens bilan_evaluation _canevas.docx

    Nombre de bnficiaires(Techniciens) A.A D NC

    Nombre de bnficiairesTechniciens bilan_evaluation _canevas.docx

    Nombre de bnficiaires(Techniciens) I.A D NC

    Nombre de bnficiairesTechniciens bilan_evaluation _canevas.docx

    Nombre de bnficiaires(Techniciens) I.G.B D NC

    Nombre de bnficiairesTechniciens bilan_evaluation _canevas.docx

    Nombre de bnficiaires(Techniciens) C.I D NC

    Nombre de bnficiairesTechniciens bilan_evaluation _canevas.docx

    Nombre de bnficiaires(Techniciens) Autres D NC

    Nombre de bnficiaires

    Techniciens bilan_evaluation _canevas.docx

    Nombre de bnficiaires

    (Techniciens) Total D CNbr de journes desensibilisation bilan_evaluation _canevas.docx Number of sensibilisation days D NC

    Nbrdleveursbnficiaires bilan_evaluation _canevas.docx Number of beneficiairy farmer D NC

    Nbr de cas de tuberculoseet brucellose bilan_evaluation _canevas.docx

    Number of cases oftuberculosis and brucellosis D NC

    Nbr de bovins abattus bilan_evaluation _canevas.docx Number of cattle slaughtered D NC

    Nbr de bovinssubventionns bilan_evaluation _canevas.docx Number of cattle subsidized D NC

    Nombre dtablesencadres et suivies sur le

    plan technique bilan_evaluation _canevas.docx

    Number of stables framed and

    followed the technical D NCNombre dtablesencadres sur le plansanitaire bilan_evaluation _canevas.docx

    Number of stables framed interms of health D NC

    Organisme USRD Name of the organism I NC Synonymy

    Sigle USRD Acronym of the organism I NC

    Ville USRD City of the organism I NC

    Nom USRD Last Name of the user I NC

    Prnom USRD First Name of the user I NC

    Adresse lectronique USRD E-mail of the user I NC Synonymy

    Profile USRDProfile of the user (cadre,technicien, insminateur) I NC

    Type USRDType of the user (ANEB user,organism user, witness) I NC

    Mois USRD Month of the activity I NC

    Anne USRD Year of the activity I NC

    Date limite USRD Deadline of the activity I NC

    Login USRD Login of the user I NC

    Mot de passe USRD Password of the user

  • 7/27/2019 Requirements Engineering Document

    45/52

    Software Engineering I Requirements Engineering Document

    45 FALL 2012

    Dictionary: Second Round

    Attributes Document Description I/D C/NC

    Nom de l'Organisme bilan_evaluation _canevas.docx The name of the organisation D NC

    Adresse de l'Organisme bilan_evaluation _canevas.docx The address of the organisation D NC

    Tlphone de l'Organisme bilan_evaluation _canevas.docx The phone of the organisation D NCE-mail de l'Organisme bilan_evaluation _canevas.docx The email of the organisation D NC

    Fax de l'Organisme bilan_evaluation _canevas.docx The fax of the organisation

    Nombre dleveursindividuels bilan_evaluation _canevas.docx

    Number of independent farmers whooperate for the concerned organisms D NC

    Nombre de coopratives bilan_evaluation _canevas.docxnumber of cooperatives operating forthe processed organism D NC

    Nombre dleveurs bilan_evaluation _canevas.docx Number of cooperative farmers D NC

    Nombre de CCL privs bilan_evaluation _canevas.docxNumber of dairy cooperatives(cooprative laitres) D NC

    Nombre dleveurs bilan_evaluation _canevas.docx Number of CCL farmers D NC

    Nombre total dleveurs bilan_evaluation _canevas.docx The total number of farmers D NC

    Nombre de circuits IA bilan_evaluation _canevas.docxNumber of Artificial InseminatorCircuits D NC

    Nombre de vhicules IA bilan_evaluation _canevas.docxNumber of Artificial inseminatorVehicules D NC

    Nombre dinsminateurs bilan_evaluation _canevas.docx Number of inseminators D NC

    Mis la disposition bilan_evaluation _canevas.docx Number of available inseminators D NC

    Recruts bilan_evaluation _canevas.docx Number of hired inseminators D NC

    IA1 Race pure bilan_evaluation _canevas.docxNumber of artificial inseminatorpurebred D NC

    IA1 - Race croise bilan_evaluation _canevas.docxNumber of artificial inseminatorcrossbred D NC

    IA1 - Race locale bilan_evaluation _canevas.docx

    Number of artificial inseminator local

    breed D NCRptitions Totales bilan_evaluation _canevas.docx Total of repetitions D C

    IA totales bilan_evaluation _canevas.docx Artificial Inseminator Totals D C

    Nbr total des leveurstouchs bilan_evaluation _canevas.docx Number of affected farmers D NC

    Contrle gestation bilan_evaluation _canevas.docx Gestation Control D NC

    Contrle naissance bilan_evaluation _canevas.docx Birth Control D NC

    Nombre Holstein bilan_evaluation _canevas.docx Number of Holsten D NC

    Nombre Montbliarde bilan_evaluation _canevas.docx Number of Montbliarde D NC

    Nombre Charolai bilan_evaluation _canevas.docx Number of Charolai D NC

    Nombre Brahman bilan_evaluation _canevas.docx Number of Brahman D NC

    Nombre BBB bilan_evaluation _canevas.docx Number of BBB D NC

    Nombre Other bilan_evaluation _canevas.docx Number of Other D NC

    Nombre race pure bilan_evaluation _canevas.docx Total of purebred D C

    Semences CRIA localespour Holstein bilan_evaluation _canevas.docx Semences CRIA locales pour Holstein D NC

    Semences importes pourHolstein bilan_evaluation _canevas.docx Semences importes pour Holstein D NC

    Total Semence pourHolstein bilan_evaluation _canevas.docx Total Semence pour Holstein D C

    Semences CRIA localespour Montbliarde bilan_evaluation _canevas.docx

    Semences CRIA locales pourMontbliarde D NC

    Semences importesMontbliarde bilan_evaluation _canevas.docx Semences importes Montbliarde D NC

    Total Semence pourMontbliarde bilan_evaluation _canevas.docx Total Semence Montbliarde D C

  • 7/27/2019 Requirements Engineering Document

    46/52

    Software Engineering I Requirements Engineering Document

    46 FALL 2012

    Semences CRIA localespour Charolais bilan_evaluation _canevas.docx

    Semences CRIA locales pourCharolais D NC

    Semences importes pourCharolais bilan_evaluation _canevas.docx Semences importes pour Charolais D NC

    Total Semence pourCharolais bilan_evaluation _canevas.docx Total Semence pour Charolais D C

    Semences CRIA localespour Brahman bilan_evaluation _canevas.docx

    Semences CRIA locales pourBrahman D NC

    Semences importes pourBrahman bilan_evaluation _canevas.docx Semences importes pour Brahman D NC

    Total Semence pourBrahman bilan_evaluation _canevas.docx Total Semence pour Brahman D C

    Semences CRIA localespour BBB bilan_evaluation _canevas.docx Semences CRIA locales pour BBB D NC

    Semences importes pourBBB bilan_evaluation _canevas.docx Semences importes pour BBB D NC

    Total Semence pour BBB bilan_evaluation _canevas.docx Total Semence pour BBB D C

    Autres Semences CRIAlocales bilan_evaluation _canevas.docx Autres Semences CRIA locales D NC

    Autres Semencesimportes bilan_evaluation _canevas.docx Semences importes Autres D NC

    Autres Total Semence bilan_evaluation _canevas.docx Total Semence pour Autre D C

    Total Semences CRIAlocales bilan_evaluation _canevas.docx Total Semences CRIA locales ? D C

    Total Semences importes bilan_evaluation _canevas.docx Total Semences importes D C

    Total Autre Semences bilan_evaluation _canevas.docx Total Autre Semences D C

    Nombre agents contrleurslaitiers bilan_evaluation _canevas.docx Number of agents dairy controllers D NC

    Nombre vhicules utiliss bilan_evaluation _canevas.docx Number of used vehicles D NC

    Nombre dunitsppinires bilan_evaluation _canevas.docx Number of nurseries units D NC

    Nbr total dtablesContrles pour Holstein bilan_evaluation _canevas.docx

    Nbr total dtables Contrles pourHolstein D NC

    Effectif total de vachesprsentes pour Holstein bilan_evaluation _canevas.docx

    Effectif total de vaches prsentes pourHolstein D NC

    Effectif total de vachescontrles pour Holstein bilan_evaluation _canevas.docx

    Effectif total de vaches contrlespour Holstein D NC

    Nombre lactationstermines dans lannepour Holstein bilan_evaluation _canevas.docx

    Nombre lactations termines danslanne pourHolstein D NC

    Moyenne lait 305 jours-kgpar lactation termine danslanne pour Holstein bilan_evaluation _canevas.docx

    Moyenne lait 305 jours-kg parlactation termine dans lanne pourHolstein D NC

    Moyenne matires grasse305 jours-kg par lactationtermine dans lannepour Holstein bilan_evaluation _canevas.docx

    Moyenne matires grasse 305 jours-kg par lactation termine dans lannepour Holstein D NC

    Nombre gnissesslectionnes dans lannepour Holstein bilan_evaluation _canevas.docx

    Nombre gnisses slectionnes danslanne pourHolstein D NC

    Nbrtotal dtablesContrles pourMontbliarde bilan_evaluation _canevas.docx

    Nbr total dtables Contrles pourMontbliarde D NC

    Effectif total de vachesprsentes pourMontbliarde bilan_evaluation _canevas.docx

    Effectif total de vaches prsentes pourMontbliarde D NC

    Effectif total de vachescontrles pourMontbliarde bilan_evaluation _canevas.docx

    Effectif total de vaches contrlespour Montbliarde D NC

  • 7/27/2019 Requirements Engineering Document

    47/52

    Software Engineering I Requirements Engineering Document

    47 FALL 2012

    Nombre lactationstermines dans lannepour Montbliarde bilan_evaluation _canevas.docx

    Nombre lactations termines danslanne pour Montbliarde D NC

    Moyenne lait 305 jours-kgpar lactation termine danslanne pour Montbliarde bilan_evaluation _canevas.docx

    Moyenne lait 305 jours-kg parlactation termine dans lanne pourMontbliarde D NC

    Moyenne matires grasse305 jours-kg par lactationtermine dans lannepour Montbliarde bilan_evaluation _canevas.docx

    Moyenne matires grasse 305 jours-kg par lactation termine dans lannepour Montbliarde D NC

    Nombre gnissesslectionnes dans lannepour Montbliarde bilan_evaluation _canevas.docx

    Nombre gnisses slectionnes danslanne pour Montbliarde D NC

    Total Nbr dtablesContrle bilan_evaluation _canevas.docx Total Nbr dtables Contrles D C

    Effectif total de vachesprsentes Total bilan_evaluation _canevas.docx Total Effectif de vaches prsentes D C

    Effectif total de vachescontrles Total bilan_evaluation _canevas.docx Total Effectif de vaches contrles D C

    Nombre lactationstermines dans lanneTotal bilan_evaluation _canevas.docx

    Total nombre lactations terminesdans lanne D C

    Moyenne lait 305 jours-kgpar lactation termine danslanne Total bilan_evaluation _canevas.docx

    Total moyenne lait 305 jours-kg parlactation termine dans lanne D C

    Moyenne matires grasse305 jours-kg par lactationtermine dans lanneTotal bilan_evaluation _canevas.docx

    Total moyenne matires grasse 305jours-kg par lactation termine danslanne D C

    Nombre gnissesslectionnes dans lanneTotal bilan_evaluation _canevas.docx

    Total nombre gnisses slectionnesdans lanne D C

    Techniciens ONSSA bilan_evaluation _canevas.docxNumber agents identificateurs (dutype Techniciens ONSSA) D NC

    Insminateurs bilan_evaluation _canevas.docxNumber agents identificateurs (dutype Insminateurs) D NC

    Contrleurs laitiers bilan_evaluation _canevas.docxNumber agents identificateurs (dutype Contrleurs laitiers) D NC

    Autres bilan_evaluation _canevas.docxNumber agents identificateurs (dutype Autres) D NC

    Vhicules OP bilan_evaluation _canevas.docxNumber of vhicules utiliss (du typeVhicules OP) D NC

    Vhicules ONSSA bilan_evaluation _canevas.docxNumber of vhicules utiliss (du typeVhicules ONSSA) D NC

    Autres bilan_evaluation _canevas.docx Number of vhicules utiliss (du typeAutres) D NC

    Nombre tables touchesdans lanne bilan_evaluation _canevas.docx Number of stables affected in the year D NC

    Nombre Bovins identifisdans lanne bilan_evaluation _canevas.docx Number of cattle identified in the year D NC

    Nombre CIAB tablis danslanne bilan_evaluation _canevas.docx

    number of (Carte dIdentification etdAccompagnement des Bovins)established in the year D NC

    Cumul de Bovins identifisdepuis le dbut delopration bilan_evaluation _canevas.docx

    Accumulated Cattle identified sincethe beginning of the operation D NC

    Anne dmarrage IGB bilan_evaluation _canevas.docx

    ('identification gnralise des bovins)

    year start D NCNombre de session/thme bilan_evaluation _canevas.docx Training number of meetings/theme D NC

  • 7/27/2019 Requirements Engineering Document

    48/52

    Software Engineering I Requirements Engineering Document

    48 FALL 2012

    A.A

    Nombre de session/thme bilan_evaluation _canevas.docxTraining number of meetings/themeI.A D NC

    Nombre de session/thme bilan_evaluation _canevas.docxTraining number of meetings/themeI.G.B D NC

    Nombre de session/thme bilan_evaluation _canevas.docx

    Training number of meetings/theme

    C.l D NC

    Nombre de session/thme bilan_evaluation _canevas.docxTraining number of meetings/theme

    Autres D NC

    Nombre de session/thme bilan_evaluation _canevas.docxTraining number of meetings/themeTotal D C

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx

    Number of beneficiaries (Eleveurs)A.A D NC

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx Number of beneficiaries (Eleveurs) I.A D NC

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx

    Number of beneficiaries (Eleveurs)I.G.B D NC

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx Number of beneficiaries (Eleveurs) C.I D NC

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx

    Number of beneficiaries (Eleveurs)Autres D NC

    Nombre de bnficiairesEleveurs bilan_evaluation _canevas.docx

    Number of beneficiaries (Eleveurs)Total D C

    Nombre de bnficiairesTechniciens bilan_evaluation _canevas.docx

    Nombre de bnficiaires(Techniciens) A.A D NC

    Nombre de bnficiairesTechniciens bilan_evaluation _canevas.docx

    Nombre de bnficiaires(Techniciens) I.A D NC

    Nombre de bnficiairesTechniciens bilan_evaluation _canevas.docx

    Nombre de bnficiaires(Techniciens) I.G.B D NC

    Nombre de bnficiairesTechniciens bilan_evaluation _canevas.docx

    Nombre de bnficiaires(Techniciens) C.I D NC

    Nombre de bnficiairesTechniciens bilan_evaluation _canevas.docx Nombre de bnficiaires(Techniciens) Autres D NC

    Nombre de bnficiairesTechniciens bilan_evaluation _canevas.docx

    Nombre de bnficiaires(Techniciens) Total D C

    Nbr de journes desensibilisation bilan_evaluation _canevas.docx Number of sensibilisation days D NC

    Nbr dleveursbnficiaires bilan_evaluation _canevas.docx Number of beneficiairy farmer D NC

    Nbr de cas de tuberculoseet brucellose bilan_evaluation _canevas.docx

    Number of cases of tuberculosis andbrucellosis D NC

    Nbr de bovins abattus bilan_evaluation _canevas.docx Number of cattle slaughtered D NC

    Nbr de bovinssubventionns bilan_evaluation _canevas.docx Number of cattle subsidized D NC

    Nombre dtablesencadres et suivies sur leplan technique bilan_evaluation _canevas.docx

    Number of stables framed andfollowed the technical D NC

    Nombre dtablesencadres sur le plansanitaire bilan_evaluation _canevas.docx

    Number of stables framed in terms ofhealth D NC

    Sigle Organisme USRD Acronym of the organism I NC

    Ville Organisme USRD City of the organism I NC

    Nom Utilisateur USRD Last Name of the user I NC

    Prnom Utilisateur USRD First Name of the user I NC

    Profile Utilisateur USRDProfile of the user (cadre, technicien,insminateur) I NC

    Type Utilisateur USRDType of the user (ANEB user,organism user, witness) I NC

  • 7/27/2019 Requirements Engineering Document

    49/52

    Software Engineering I Requirements Engineering Document

    49 FALL 2012

    Mois Activit USRD Month of the activity I NC

    Anne Activit USRD Year of the activity I NC

    Date limite Soumission USRD Deadline of the activity submission I NC

    Login Utilisateur USRD Login of the user I NC

    Mot de passe Utilisateur USRD Password of the user I NC

    Synonymy:

    Nom de l'Organisme/Nom Organisation

    E-mail/Adresse Electronique

    Homonymy:

    "Nombre" for holsten appears in " bilan_evaluation _canevas.docx";

    "Nombre" for Montbliarde appears in " bilan_evaluation _canevas.docx";

    "Nombre" for Charolai appears in " bilan_evaluation _canevas.docx";

    "Nombre" for Brahman appears in " bilan_evaluation _canevas.docx";

    "Nombre" for BBB appears in " bilan_evaluation _canevas.docx";

    "Nombre" for Other appears in " bilan_evaluation _canevas.docx";

    "Nombre" for Total appears in " bilan_evaluation _canevas.docx";

    "Holstein" for "Nbr total dtables Contrles" appears in " bilan_evaluation _canevas.docx";

    "Holstein" for "Effectif total de vaches prsentes" appears in " bilan_evaluation _canevas.docx";

    "Holstein" for "Effectif total de vaches contrles" appears in " bilan_evaluation _canevas.docx";

    "Holstein" for "Nombre lactations termines dans lanne" appears in

    "bilan_evaluation_canevas.docx";

    "Holstein" for "Moyenne lait 305 jours-kg par lactation termine dans lanne" appears in

    "bilan_evaluation _canevas.docx";

    "Holstein" for "Moyenne matires grasse 305 jours-kg par lactation termine dans lanne" appears in"bilan_evaluation _canevas.docx";

    "Holstein" for "Number gnisses slectionnes dans lanne" appears in

    "bilan_evaluation_canevas.docx";

    "Montbliarde" for "Nbr total dtables Contrles" appears in " bilan_evaluation _canevas.docx";

    "Montbliarde" for "Effectif total de vaches prsentes" appears in " bilan_evaluation _canevas.docx";

    "Montbliarde" for "Effectif total de vaches contrles" appears in " bilan_evaluation _canevas.docx";

    "Montbliarde" for "Nombre lactations termines dans lanne" appears in "

    bilan_evaluation_canevas.docx";

    "Montbliarde" for "Moyenne lait 305 jours-kg par lactation termine dans lanne" appears in

    "bilan_evaluation _canevas.docx";"Montbliarde" for "Moyenne matires grasse 305 jours-kg par lactation termine dans lanne"

    appears in " bilan_evaluation _canevas.docx";

    "Montbliarde" for "Number gnisses slectionnes dans lanne" appears in

    "bilan_evaluation_canevas.docx";

    "Charolais" for "Nbr total dtables Contrles" appears in " bilan_evaluation _canevas.docx";

    "Charolais" for "Effectif total de vaches prsentes" appears in " bilan_evaluation _canevas.docx";

    "Charolais " for "Effectif total de vaches contrles" appears in " bilan_evaluation _canevas.docx";

    "Charolais " for "Nombre lactations termines dans lanne" appears in

    "bilan_evaluation_canevas.docx";

    "Charolais " for "Moyenne lait 305 jours-kg par lactation termine dans lanne" appears in"bilan_evaluation _canevas.docx";

  • 7/27/2019 Requirements Engineering Document

    50/52

    Software Engineering I Requirements Engineering Document

    50 FALL 2012

    "Charolais " for "Moyenne matires grasse 305 jours-kg par lactation termine dans lanne" appears

    in "bilan_evaluation _canevas.docx";

    "Charolais " for "Number gnisses slectionnes dans lanne" appears in

    "bilan_evaluation_canevas.docx";

    "Total" for "Nbr total dtables Contrles" appears in " bilan_evaluation _canevas.docx";

    "Total" for "Effectif total de vaches prsentes" appears in " bilan_evaluation _canevas.docx";

    "Total" for "Effectif total de vaches contrles" appears in " bilan_evaluation _canevas.docx";

    "Total" for "Nombre lactations termines dans lanne" appears in "bilan_evaluation_canevas.docx";

    "Total" for "Moyenne lait 305 jours-kg par lactation termine dans lanne" appears in

    "bilan_evaluation _canevas.docx";

    "Total" for "Moyenne matires grasse 305 jours-kg par lactation term ine dans lanne" appears in

    "bilan_evaluation _canevas.docx";

    "Total" for "Number gnisses slectionnes dans lanne" appears in

    "bilan_evaluation_canevas.docx";

    Due to the fact that the client wants a dynamic hierarchy, attributes from "Nombre dleveurs

    individuels" to "Nombre dtables encadres sur le plan sanitaire" will be c onsidered as dynamic

    attributes since this was a requirement stated by the client.

    Hence, such attributes will be included in a recursive entity entitled "RUBRIQUE", and the latter will

    gather the name, the type, the size of the "rubrique", whether a value will be assigned to it or not (the

    field called "IS_CHAMP" in the ERD), and which "sur rubrique" it belongs to (Recursive relationship).

    ERD

  • 7/27/2019 Requirements Engineering Document

    51/52

    Software Engineering I Requirements Engineering Document

    51 FALL 2012

    Description of the ERD

    The "ORGANISME" has many "UTILISATEUR", and an " UTILISATEUR " might belong to one, and only

    one " ORGANISME ". At the same time an " UTILISATEUR of type "ANEB" or "Tmoin" shall not belong

    to any "ORGANISME". An "ORGANISME" will have a number of "RUBRIQUE" occurrences, and the

    recursive relation in "RUBRIQUE" allow to have the structure mentioned in the USRD. A "RUBRIQUE"

    might have several "SUB-RUBRIQUES", that's why we stress on the "PARENT-RUBRIQUE" rather than

    "SUB-RUBRICS".

    When "ACTIVITE" is submitted, we capture which "ORGANISME" & "RUBRIQUE" are involved, the

    intersection of both is a "VALEUR", and "ACTIVITE" entity tells us which month of which year

    "VALEUR" is alimented.

    "TYPE" & "PROFILE" are two entities that allow the dynamic maintenance of ("ANEB", "ORGANISME",

    "TEMOIN"), and ("CADRE", "TECHNICIEN", "INSEMINATEUR") values, respectively [Prospective

    Process Compatible].

    CPM-CDM Matching

    "Manage Organisms" process will interact with ORGANISME, and RUBRIQUE entities.

    "Manage Users" process will interact with UTILISATEUR, and ORGANISME entities.

    "Manage Activities" process will interact with ACTIVITE, RUBRIQUE, ORGANISME, and UTILISATEUR

    entities.

    "Manage Report" process will read only data from RUBRIQUE, ORGANISME, ACTIVITY entities and

    yields, on the fly, a graphical interface that shows data.Through the CPM-CDM matching, we can see that the CDM is complete.

    Conclusion

    For the time being, the requirement engineering allowed us to reach the exact need expressed by

    the client. As a matter of fact, a huge difference of understanding between what the client initially

    stated (Feasibility Study), and what we inferred from the client. The critical effort undertaken during

    the USRD phase decreased the size of ambiguity and erroneous assumptions made along the

    Requirement Engineering Process.

    Now, we know about the building blocks on which we will focus our efforts, the data model that

    illustrates that will interact with processes, and we already have a clear idea about the different

    users of the future software.

    Our next focus (Non Functional Requirements) will be the design and implementation of the

    application: the ultimate goal of Software Engineering. Our preliminary idea about the tools would

    be the usage of MS Access for the persistent data management, HTML for the presentation layer and

    Java Standard Edition for the overall business logic.

  • 7/27/2019 Requirements Engineering Document

    52/52

    Software Engineering I Requirements Engineering Document

    Annex

    bilan_evaluation_canevas.docx

    Ralisations2010.xlsx

    Ralisations_2010_organisations_prof_an