Here's a high level diagram about software development . In particular , here's how the process flow works in FINANCE application

1. 1. ANALYSIS
• Feasability at Low-Level/Req.s Analysis
• Business Analysis
b1) Functional Analysis
b2) Non-functional Analysis – Quality
• Domain Analysis
constraints on the system from the domain of operations
(Architecture etc)
Customer
ACCEPTS
CUSTOMER signaling bugs
Customer’s validation
changes to the software and
related documentation
5. PRODUCTION
PRODUCTION ENVIRONMENT (Software , Hardware)
DEVELOPMENT ENVIRONMENT (Software , Hardware)
Version 0.1
Version 0.2
Version 0.3
Version 0.4
.
.
.
.
.
.
.
.
.
4. TESTING
• Single activity test
• Integration test
-Functional test
-Performance Test
-Breaking Test
-Regression Test
-Safety Test
-Accessibility Test
-Acceptability Test
-etc….
Customer
• Business Analysis Team
• PM and other entities
(I-B) Or will i do?
BA
Standard
(Legal/Quality)
Standard Respect Needs
(1) Customer’s requirements are sent to the supplier
PM starts «exceling» the Project and keeps monitoring
all the relevant forman communications (email etc)
(I-A) Will you transmit a reply to the customer?
PM
TRANSFER OF INFORMATIONS (I.E. High Level Feasability)
(I-B)
(II-B)
Transfer of feedback to the customer : highest level feasability
PM agrees with the customer a baseline for BR and SP
Communications
Communications
PM keeps monitoring , updating its monitoring plan (excel/project)
BR
Supplier
• Business Analysis Team
• PM and other entities
Customer
• Business Analysis Team
• PM and other entities
V
a
l
i
d
a
t
i
o
n
Brainstorming
Meeting
BR is already validated
(3) Feasability Analysis (MID-LEV)
(2) Production of the BRD – Business Requirements Document
• Matches economical/financial requirements with budget constraints
• Evaluation of the general feasability at a middle-level
BRD production timeline SPD production timeline
(4) Production of the SPD – Solution Proposal Document
• Mid-lev Business requirements
• Cost/Time estimate
• Economic Offer
PM BA
SALES TEAM
Edit request
IT Board
Customer’s validation
• Customer’s extimation approval
• Customer accepts the economical offer of the SPD
(4) Project Charter
SP 2. PLANNING
• WBS of
b1) Architecture (Design Pattern Project)
b2) Detailed Project
b2) Software Localization
• Activities Scheduling
• Resource Allocation
3. DEVELOPMENT
• WBS of Implementation
a) Single activities
b) Integration of each part
• Technological Choice
a) Product
- Coding Language
- Libraries
- Scripting Languages
- DataBase
- Internet
b) Process
- Editor
- Compilator (or an interpreterforthe testing process)
- Automatic Building
(I) Source-code auto-compil in binary
(II) Binary code packaging
(III) Source-code auto-compil in binary
(IV) Auto-test/ auto-compilation
(V) Deployment
(VI) Documentation and/or notes(Tools like Docsee , Doxygen , JavaDoc)
- Debugging (Tools like Docsee , Doxygen , JavaDoc)
(I) Error/Buganalysis
• Technical Tests (Debugging+other)
DEBUGGER
Errori di semantica etc
COMPILER EDITOR
software
GUI Processing
Logic Data
Management
Revision Control System Register
(SubVersion , GIT)
TESTING ENVIRONMENT (Software , Hardware)
BUG TICKETING MANAGER
-Bug/Bug fixing register
DEV to TEST deployment
TEST to PROD deployment
SOFTWARE release
SYSTEM TEST
(FUNCTIONAL+NON
FUNCTIONAL)
CUSTOMER TEST
Customer’s edit request
Deployment type :
a. DIRECT INSTALLATION
b. PARALLEL INSTALLATION
c. STAGGERED INSTALLATION
d. PILOT INSTALLATION
6. MAINTENANCE
Customer
ACCEPTS
7. SOFTWARE EOF