Autumn 2014, NetCracker Student Practice Task
Internet provider
Оглавление
Internet provider “Flower” 3
Target 3
Approach 3
Description 3
Related documentation 3
Table of abbreviations and shortened names 3
Functional Requirements 3
Registration and user management 3
User roles 4
Placing request 4
Availability Check 5
SO workflows 6
RI management 7
E-mail notification 7
Integration with 3rd party systems 7
Reports 8
Non-Functional Requirements 8
Data preparation 8
Assumptions and out of scope 8
Internet provider “Flower” Target
Develop OSS system for internet provider “Flower” that will be full-cycle service provisioning with the usage of self-service portal.
Approach
Development should be splitted into following areas:
DB development (SQL, PL/SQL). Oracle XE should be used as DB.
Middle-layer development (Java). EJB2.0 + GlassFish should be used.
Front-end development (Java, JavaScript, HTML, CSS). No Java frameworks should be used, JS frameworks are allowed.
System should be hosted on cloud system. Integration with at least one external system is mandatory for development.
Description
System is a web-based tool that is used for applying for a service and it’s provisioning.
Basic operation items are Service Instance, Service Order.
Related documentation
The following documentation should be delivered with the code and working software;
plan
report (weeklyorcumulative)
lowleveldesign (softwarearchitecturedesign)
usecases – diagramsanddescription
DB ER-diagram
traceabilitymatrix
teststrategy
testcases
Documentation should be provided in English.
Table of abbreviations and shortened names
Abbreviation |
Interpretation |
User |
End-user of the system (Customer, “Flower” representative) |
SO |
Service Order |
SI |
Service Instance |
RI |
Resource Inventory |
CA |
Customer Account |
Functional Requirements
Registration and user management
Req## |
Requirement description |
Priority |
NC.KYIV.KMA.2014.FLW.REG.1 |
Next user roles exist in the system: Administrator, Customer Support Engineer, Provisioning Engineer, Installation Engineer, Customer User |
M |
NC.KYIV.KMA.2014.FLW.REG.2 |
Customer can register in system himself |
M |
NC.KYIV.KMA.2014.FLW.REG.3 |
Provider employee accounts are created by an Administrator. |
M |
NC.KYIV.KMA.2014.FLW.REG.4 |
Account blocking is performed by an Administrator |
O |
User roles
Req## |
Requirement description |
Priority |
NC.KYIV.KMA.2014.FLW.ROL.1 |
The system should provide possibility to any user from Internet to register as Customer User |
M |
NC.KYIV.KMA.2014.FLW.ROL.2 |
Customer Support Engineer is able to change Customer User password, review Service Instance and Service Order for Customer User |
M |