What?

Quinn's Competing values Framework 2


RECOGNIZED MODIFIED AND DEVELOPMENT CONTROL

– Develop a multi-skilled development team
– Setting the Goals and Goals
– A common perspective on development
– Role and resource capability
– Inventory of opportunities and resources
– Systemic development process and knowledge management
– Determined progress and guidance


NETWORK SERVICE AND SOFTWARE

  • The community software (group wareTikiWiki acts as an information service platform for intra- and extra-community
  • Training & Learning space OPPIMO has been implemented on Moodle
  • As a publishing system (including blogs), WordPress is enabled
  • Open Code and Free Software Tools for Information Processing and Documentation; LibreOffice, GIMP, and Inkscape

SERVICE MARKET

– BLOG Gallery
– OPPIMO  T&L Space
– CONSULTING
– workshop
– design
– mentoring
– community


ORGANIZING PROJECTS

The project to be started must be carefully prepared. Representation of all actors involved in the project is desirable already at the stage of preparation. The project plan must be accompanied by a so- the project contract, which is recognized to be involved in each party’s roles, responsibilities and obligations. Participation must be clearly recorded, as well as utilizing the results of the project.

The development of an information system must be divided into clear, timing and resource-based development cycles.

Deployment of System Development

Project Management; Projects, Contracts and Startup .
Pre-Design: Conceptualization, Inventory and Requirements (in conjunction with users’ representatives).
– Software / System / Content Service Configuration: Architecture and Usage (Implementation Limitation).
Functional design: User interface, logic, application logic.
Technical design by sub-area: Network, Device and Software Engineering.
Application Design: By Function Area and Modules.
Evaluation and Programming: Arranging Programming, Application Programming, Compilers and Programs.
Module testing: By operation and / or by function.
Integration: Combining modules into a functional entity.
System Testing: Piloting, Beta Versions, etc. Test Drivers and Usability Testing.


INITIATIVES IN SOFTWARE AND INFORMATION SYSTEM DEVELOPMENT PROJECTS

1. description of the subject area of ​​the application
2. user definition; roles / users
3. description / usage of the future application
4. Functional description of the activities implemented by the system / programs
5. the rough architecture and structural diagram of the system / arrangement
6. system composition; modules, components and components
7. Characteristics and characteristics of the application / application
8. Usability requirements from users’ point of view
9. functional requirements of the application and its applications
10. technical requirements; technology, hardware and operating environment for implementation and use environment
11. competence requirements for developers; competence areas and qualifications
12. the boundary conditions of implementation; time, resources and rough budget estimates


– partnership model under construction 


contact: Matti Pyykkönen              ©2018 DigiTILA