MuSMo’s project, in our opinion, is considered to be a medium-to-large project that involves i) distributed environments, ii) significant amount of computational power and storage, iii) different data types that must not be treated equally, and iv) fairly complex business logics. It is definitely not a project to be taken lightly. Over a year working with a software development company, we have the following take aways specific on application development.
-
Framework. Always work with an application framework. Choose the most suitable framework for your project. In other words, contextualise on how flexible, extensible and adaptable your project will be and how it relates to the framework you are working with. Do not neglect to take into account the original purpose of the framework, its security risks, documentation and resource availability.
-
Discussion. Development is not an individual effort, it is a team effort. And thus it requires on-going discussion of the project tasks on its requirements and specifications to ensure highest quality of clarity. If the team does not understand the task fully before acting, it will only lead to unnecessary reiterations.
-
Documentation. Without clear and detail documentations, it would be extremely difficult and time consuming to i) keep track on the project’s status, capabilities, components, features, functions, etc., ii) generate mature discussions on tasks, and iii) pin-point any potential and/or existing issues.
Our previous post on Outsourcing Software Development is intricately related to this post.
0 Responses to “2008-2009 Take Aways: Application Development”
Leave a Reply