Personal Learning Management Sylvia Rene’ Cozier PRE/211 September 9, 2013 Vic Achievers The question at hand; is it possible to design an application to record high economic value learning tasks or insights that will allow for periodic review? Yes it is possible, yet there is a level of complexity to design such an application. To solve the problem the application needs to determine economic value or insight that will allow for review the important lessons learned.
Each task would need an attribute, assigned a alee or a score to identify which may be of more significance than another. To achieve the output value the application would be dependent on key user input. For the application to be user friendly and obtain the required input the application must contain the ability for the user to input lessons learned with responses. Set reminder triggers for reviewing and revisiting those lessons on a periodic basis. The user would need to be able to select a value or score for the element they are entering to give it a scoring level.
The user interface would need about 8-10 input fields for the user, a couple calculated display fields, search field, date and time fields with calendaring, and an output list component. A small backbend database would be needed to store the data and information into a structure that can be queried upon when needed. Important lesson data, date of the lesson, time, and open text area to write what important points were learned from the lesson. A score factor or attribute needs to be stored with each record to provide the overall calculated economic value.
The database would be queried for content and score values to provide output to the user once data had been entered for reference. The development activities would begin with the planning and requirements phase where all of the application flow, modules and calculations would be defined in detail along with some pseudo-code to clarify all of the calculations, input, process and outputs. Implementation of the application would be the actual coding of the application into a running, functioning application.
Once the application is implemented it would then be tested, debugged and tested again. Once all this is complete, documentation would be completed and any additional documentation for the application from the user perspective would be done for deployment and maintenance of the application. The program will be developed using object-oriented programming. This decision is based on the need for the program to have several components on the project, ease of use and time constraints. This approach is being taken in order to minimize coupling and make maintaining the application easier.
The key components of the object-oriented approach which are useful to our application are encapsulation, class and inheritance, methods and messages, and instances and instantiation. Using this approach a structure can be created representing classes and objects and values Selenga or Innervate. It Is ten goal AT ten program to use ten values Trot a specials lesson and rate its economic viability. Sense our application is largely based on values derived from calculations from user input object-oriented appears the best hospice.
In summary the application is possible with the object-oriented approach and best practices implemented. To develop the full application it would need a small back end database with fields that a user or rule could query based upon an economic value. REFERENCES: Based on object-oriented application design best practices which are discussed in several areas such as the Code Project (www. Coder]etc. Com) , skillets module Getting Started with Software Programming, EBOOK collection: Prelude to Programming. Concepts and Design, Fifth Edition