The document summarizes Syed Aqeel Jaffary's learning portfolio for a project management system. It describes researching two technologies (Intelledox and Joget) for the project, with Joget being selected for its flexibility and features. It outlines meetings, work distribution among team members, and the system model developed. Key achievements included account registration, a projects data list, and populating a website. Lessons learned included the importance of communication, avoiding delays, and focusing efforts on a single technology.

1. Learning Portfolio
Comp-8715
(TechLauncher Management System)
Syed Aqeel Jaffary
u5496296
1st-Semester-2015
Week-8 onwards

2. Introduction
• Architectural Design of project
• Technologies Comparisons
• Team Meetings
• Distribution of work
• Project Model
• Requirements

3. Architecture

4. Technology Research
• Intelledox
 Documents creation through web forms
 Do not covers our project scope
 Intelledox is just a document creation system
 What kind of security for Intelledox? Can you log in?
 Can't demonstrate core functions and proper model
 Build something to play with, so we know what we can focus on
 Can’t Integrate data from current system for testing
 Can’t store data for future use
 Can’t create users or projects
 Can’t implement actual model
 Only support IE browser
 No security provided for data insertion

5. Technology Research cont..
• Joget
 Open Source
 Platform Flexibility
(Windows, OSX, Linux)
 Browser Flexibility
(Chrome, Firefox, IE, Safari)
 Forms-based Web
Applications
 User management
 Platform
 Enterprise mobility
 Plugin architecture
 Build and run web-based
app
 Web based UI
 Easy deployment
 Workflow management
 Forms
 Data lists
 User views
 Integration

6. Meetings
• Team Meetings
 Twice in a week
 Worked in small teams
 Resolves issues of each others
 Actual implementation after testing and Team leader
approval.
• Client Meetings
 Once in a week
 Requirements Gathering
 Feedback on work
 Future tasks Discussions

7. Work Distribution
• Intellidox Team
 Try to implement some function on intellidox
 Communication with Intellidox team to get solutions
 Work on class diagram rather than model
• Joget Team
 Design Model
 Create Forms
 Database Connectivity
 Workflows implementation
 Developed dummy system
• Team Leader
 Assigning tasks
 Document writing
 Requirements gathering
 Worked on Amazon Server setup
 Used Gitlab for version control
 Trello board used for task management

8. System Model

9. Value Of work
• My Own research and Work:
 System Architecture understanding
 Develop System Model
 Work on Joget platform with which we succeeded
 Work on data lists for participants and projects
 Design and develop different forms.
 Work on user view
 Dummy forms and data lists of
Expressions of Interest

10. Team Members Participation
• Three of us were working on JOGET including our
team lead.
• Team Lead did responsibly all of his duties
 Task allocation
 Managing workflow
 Requirements gathering and implementations
 VM servers management and deploy system on
AMAZON
 Login forms workflows
 Email notifications

11. Team participation Cont..
• Intellidox Fails:
Prototype only implemented on Joget workflow system.
Why not both?
● Technological issues
● Schedule delays
● Developmental constraints
Decision to focus on a single system.

12. Achievements
Planned:
● Account Registration
● Projects Data Lists
● Allow users to
○ edit created
information
○ express interest in
projects (dummy)
○ create projects
Extra:
● Website population
○ display participants
○ display projects
● Account
security/permissions
● Admin control

13. Key Lessons
• Work together to share
ideas and implementation
• Divisions of tasks to
speedup the work
• Don’t leave stuff for end
• Don’t experiments, better
to discuss with team
• Communicate in time
regarding to any issue
• Client should be updated
• Be multi-task
• Understand the problem
• Client should be clear
about deliverables
• Don’t waste time with
technical issues, better to
work with others on
different tools
• Keep pushing the lazy
team members
• Motivate team members
for quick and better
results

14. Changed Attitude
• Knowledge
 Knows what to do
 Understanding of problems
• Skills
 How to resolve and handle issues
 Management
• Attitude
 Wants to do?
 Get rid off
 Responsibility

15. Thanks