Requirements Monitoring
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
Still loading...
ABCDEFGHIJKLMNOPQRSTUV
1
#
TypeDenominationPriority (1->5)DescriptionStateStart SprintEnd SprintValidatedComments
2
1MonitoringUsing SCRUM method1Use this Agile method to monitor the project, working with short sprints / demo-drivenDone17Yes
3
2FunctionnalList Edition1Edit a local list, by adding or deleting fragments
Done22Yes
4
3FunctionalList Fetching1Allow clients to fetch a list stored by a serverDone34Yes
5
4FunctionnalSynchronization1Synchronize the transformations done by the clientsDone26Yes
6
5ArchitecturalJupiter System1Implement the Jupiter systemDone16Yes
7
6FunctionalConflicts Handling1Handle the potential conflicts between the various transformsDone16Yes
8
7FunctionalConsole Interface1Allow to control the server and manipulate the list client-side through console commandsDone35Yes
9
8FunctionalClient Interface2Offer a user-friendly Web interfaceDone47Yes
10
9FunctionalBack-Tracing / Undo3Keep track of the transforms tree to allow back-tracing or undoCancelledYesNot natively supported by Jupiter systems
11
10FunctionalOffline Support3Handle offline edition and synchronizatin after reconnectionCancelledYesWould be interesting to implement though, but lack of time
12
11ArchitecturalScalability2Handle a varying and unknown number of clientsDone56Yes
13
13Non FonctionalErgonomy1Must be easy to useDone47Yes
14
14Non FonctionalReliability1The application should avoid data-loss or corruption, and at least offer a clear warning in case of impairmentDone17Yes
15
15Non FonctionalReusability2Components must be implemented in a way that they can be reused later, for other purposesDone17Yes
16
16Non FonctionalMaintability2The system must be able to easily integrate remote patches and new extensions (functions, ergonomy...).Done17Yes
17
17Non FonctionalSecurity3Confidentiality and private life must be ensured thanks to the appropriate protocolsDone67Yes
18
18Non FonctionalRisk Management3Risks threatening the projects must be analyzed and taken into consideration, to be prevented or correctly handledDone17Yes
19
19Non FonctionalRequirements Monitoring1Expectations must be met
Done17Yes
20
20Non FonctionalTraceability2Change impact analysis, traceback of code, regression test selection, requirements validationDone47Yes
21
21FunctionalFile Persistency4Regularly saving the document, server-sideDone66YesMongoDB
22
21FunctionalSticky Notes Demo2Demo for the project's presentation, showing an application of our Jupiter system, the manipulation of "sticky notes"Done56Yes
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
Loading...
 
 
 
Sheet1