Questo contenuto è disponibile in Italiano
QUOTE
When a client asks us to develop a custom project, we first assess with the client whether an analysis document exists.
An analysis document is an extremely detailed document that follows a set of specifications that we will go over in detail below.
If this analysis document does not exist, a preliminary interview is conducted during which we try to understand what the goals of the project are.
From this interview comes an initial quotation, that is, an outline quotation, often also with a range that defines somewhat the scope of the project: the time frame and, indeed, an order of magnitude of budget.
If, on the other hand, there is an analysis document, a different route is taken. One first assesses the level of analysis the document has achieved.
We divide the analysis papers into three levels:
The level one document is defined as an initial outline quotation and a set of tasks to be performed, among which is the definition of the level two and three analysis document.
If a level 2 document already exists, a quotation is made, a list of tasks is made, and the realization of the level 3 analysis document detail is defined among these tasks.
If, on the other hand, you decide to start with a *quotation* without an analysis document, the client, if he or she decides to accept the *quotation*, which usually includes an initial quotation for writing the analysis document as well, signs a contract.
We start with an invoice to begin work and carry out a first level of analysis; accordingly, we proceed with the second and third levels.
When you have a complete document with all three levels, you actually have a detailed task list, a precise budget, a precise specification, a Gantt, and a defined set of actions.
In general, you also have a working prototype with diagrams and, let’s say, clickable features of the interface that allow you to understand how much and actually you are going to develop.
At this point, you can draw up a cost estimate, a work schedule, a Gantt, and, in fact, a feature list. You are then ready to sign this second contract and begin the software development phase.
DISCOVERY & DESIGN PHASE
The phases of **Design and Discovery**, or rather **Discovery and Design**, are basically three:
1. The design phase at level 1,
2. The design phase at level 2,
3. The **Design System** phase, or rather the **System Design** phase, and the output phase, which is the prototyping phase.
As mentioned, in the first phase you come from a solution quotation. The Quotation involves a pre-analysis document that is, in fact, an interview with the client reported in the document.
It also includes a project charter, which is a response to pre-analysis documents with a list of features, affixes, or objectives.
There is also a maximum budget, which can be expressed in the form of a range, and a working time frame with expected timelines for project development. The level 1 design phase, which we might call **Discovery**,
THE LEVEL 1 DESIGN PHASE IS REFERRED TO AS THE DISCOVERY & DESIGN (D&D) PHASE.
Activities such as:
– Analysis of UX research
– Development of wireframes of the solution
– User flow of the various cases
– Analysis of user personas
– List of various use cases
– Differentiation of the various business logic of the application
– List of expected outputs (expected output)
– List of required integrations (integration needed)
– Area of information architecture, when expected
– – List of security privacy requirements of the project.
Information Architecture, or IA, is certainly an important aspect for all custom applications.
In particular, it assumes key importance for website-type applications, then projects that have communication and information management as their primary objective.
Information Architecture
Information architecture (IA, short for Information Architecture) is the logical and semantic organization of information within any complex information space, whether physical or digital. In other words, information architecture is concerned with how information, documents, goods and services are organized within complex spaces to facilitate wayfinding (“orientation”), findability (lit. findability of information), usability and understandability of information itself.
THE LEVEL 2 DESIGN PHASE: FUNCTIONAL DESIGN
Design phase two involves more definition of the technical and IT aspects of the solution and includes:
– modeling of the database tables
– relationship between records
– possible integrations with external APIs with details
– possible exposure of internal APIs with specifications
– other integrations with external software and systems
– a detailed design Gantt
– the development of the interface UI and components and the Design System
THE LEVEL 3 DESIGN PHASE: SYSTEM DESIGN
In phase three of the project, we go into even more detail with the technology and software architecture.
– Detail of fields in the db tables
– Choice of technology stack
– Hosting specifications
– Security specifications for DRP (RTO and RPO required)
– Support SLAs required
FINAL OUTPUT OF THE D&D PHASE
At the end of this phase, which, as mentioned, can last from one to three months, you get as output:
– a working prototype,
– a project plan detailed in all details, both from an economic point of view, so an accurate estimate,
– and from a descriptive functionality point of view,
– the final complete project Gantt,
– and a clickable prototype in Figma.
Development
After the D&D phase, the client receives a detailed quote and detailed work plan.
At this point, he is still able to stop the project by paying for the D&D phase, but not continue; or he can choose to continue according to one of the two methodologies offered, i.e., agile methodology and watefall methodology.
The quote will be formulated with a monthly progress billing (SAL) system.
However, development is done by two-week sprints, with a periodic staged release until the final version is released, which must then be tested and authorized. Only when testing is signed is the balance invoice issued.
The product is issued with a 90-day warranty from defects.
Source code is released only upon settlement of the invoice, then after testing. Throughout the time of development, the software is the property of the software house, which can release source code early to the customer, only in the case of early termination of the contract and balance of what is due of the SALs already carried out.
In the case of insolvency of one of the SAL factors, the development process stops and can be terminated or suspended until the balance comes.
WATERFALL METHOD
The waterfall method, which is more suitable for call and closed-digit projects, normally takes longer to release results and does not involve major changes during development.
It does, however, offer greater control over the budget and certainty of final costs.
FULL-AGILE METHOD
The full agile development method, on the other hand, is based on a progressive definition of scope and, as a result, less control over the total cost of the project and still less predictability.
It does, however, offer the advantage of faster release and the ability to be able to change the scope of the project as it progresses.
Questo contenuto è disponibile in Italiano
