How to technically approach and design a web product adhering to objectives?

[WeyardWiz]

Suppose you join a development team and they are working on a web visualization product developed in ASP.NET, HTML, CSS, Angular, SQL Server, and C# that provides data insights to doctors (i.e. ROI, revenue, best brands vs worst brands, etc.), as well as internal users.

The team prides itself with the following technical qualities: Quality, Reliability, CI/CD (Continuous Integration and Delivery), as well as Technical Acumen

Therefore, as part of the characteristics above that define the team, you should adhere to the following objectives:

• Ensure that the code/website will be developed superbly and with high quality
• Ensure proper security in place for authorized user access across environments (For instance, the Quality Assurance team taking the build into their environment)
• Provide constant Feedback to dev users (For example, when builds fail to compile, or performing inspections)
• Delivering reliably yet continuously value to the end-users

How would you technically approach and design this product?

• For instance, What technologies would you choose to develop this product with? (i.e. OnPrem, Cloud, Azure, AWS, etc.)
• What assumptions would you have in place?
• What questions could possibly be asked and what are the answers?
• Finally, in lieu of the defined objectives above, how do you visualize the final development pipeline and how does each part of the pipeline envisioned aim to achieve the objectives listed above?

To clarify, I am not asking or expecting any code. This is just for brainstorming purposes

[dev7060]

Being a sophomore I think I am not experienced enough to answer this, but I'd add my 2 cents from imagination.

I think the main part would be to figure out what does the team want you to do in the whole process and focus on the same. Of course, everyone in the team would be responsible for something. Making a robust product would require lots of testing. "High quality" is a broad term. It may include fast performance, less memory usage, security, usage of the best optimum algorithms, analyzing space and time complexities, etc. When you know well enough at what level your product would be there, the only thing then left would be to chase to that level keeping the time limit in mind. I'd go with one of those development life cycle models to make sure everything gets done properly.

The selection of technologies would depend on the type of project, budget, and other factors such as what has been used by the team earlier and in what field the team is comfortable working with and if there's a requirement to learn something new.

Major questions regarding the project should have been asked already in the early stages while it is being designed considering the requirements in mind. I'd use something like UML for designing the mind map or blueprint.

[WeyardWiz]

oh this is great! thank you for your input.

Could you expand on the UML diagram part? what actors, entities, functionalities and relationships would you consider/include in such a diagram? What assumptions would you make in the design?

as for time/pace complexity, could you give examples of what considerations should be in mind for the website? Im thinking scalability could be one, especially with the other question being what technologies should be used, in which cloud technologies like AWS or Azure would best fit this criteria of scaling and dynamic resource allocation.

[dev7060]

Could you expand on the UML diagram part? what actors, entities, functionalities and relationships would you consider/include in such a diagram? What assumptions would you make in the design?

Books and docs.

as for time/pace complexity, could you give examples of what considerations should be in mind for the website? Im thinking scalability could be one, especially with the other question being what technologies should be used, in which cloud technologies like AWS or Azure would best fit this criteria of scaling and dynamic resource allocation.

Again everything depends on the project. There are always general best practices to keep in mind. Rest can only be discussed if the specifics are known.