Qualcomm provides softwares to many of its clients for deploying software updates to sims. it needs 3 seperate applications with lot of manual processes to do so.
it integrates a disjoint workflow by a web based application that not only serves as a repository and version control but makes it convenient and easier way to deploy
Introduction
Workflow management is not so much about processes and time lines but about clear communication. Projects get deployed version after versions. WAC helps teams stay informed, updates about files updated tasks etc.
Workflow management allows business managers to coordinate and schedule activities of organisations to optimise the flow of information or operations between the resources of the organisation.
The coordination of these operations can be difficult, particularly if the operations are distributed over many geographically separated institutes.
In these environments there can be severe constraints both of time and budget so that controlled management of the inherent workflow processes becomes paramount.
DIAGRAM EXPLAINING THE SYSTEM OF REPOSITORY AND DEPLOYMENT
A workflow is a depiction of a sequence of operations, declared as work of a person, work of a simple or complex mechanism, work of a group of persons, work of an organization of staff, or machines. Workflow may be seen as any abstraction of real work, segregated in workshare, work split or whatever types of ordering. For control purposes, workflow may be a view on real work under a chosen aspect, thus serving as a virtual representation of actual work.
Workflow software aims to provide end users with an easier way to orchestrate or describe complex processing of data in a visual form.
Web based project management designed to quickly upload projects and version control, upload and edit files in teh projects, deploy files and folders, get back to an older version.
The focus of this design is the ability to have everyone involved in a project on the same page. Whether you’re the client, team member, developer, manager or CEO, you can easily see the status of the project.
Most project management software takes a project-centric view of the data. A project with its sub-projects is considered to be a closed unit in itself, which can be considered in isolation. Of course, this does not accurately reflect most real world situations.
Projects share resources, and the managers responsible must allocate resources across different projects. More often than not resources are shared across multiple projects. Software that considers a project to be a complete entity is unable to cope with this complexity, since one project knows nothing about the other. For instance a resource that has been allocated to work on one project, may well be over allocated to work on another, since the two projects (usually stored in separate files) are unaware of each other.
Features of WAC
1.Project-centric software introduces a complicated system of merging, importing and sharing resource related data across multiple project files. The end result is a nightmare for the average user, and has led to the proliferation of “gurus”, experts in the arcane details of juggling features in such software.
2.
TexPlanner focuses, instead, on the user as the basic unit. Users may have several projects on their plate at any time. Multiple users may have stakes in the same project. To match this situation, TexPlanner uses views.
A user’s view is the set of projects that he is involved with currently. This view may contain parts of a larger project. A project may be shared with another user by making it accessible in his view.
The key point is - regardless of the view, the fact that a resource is allocated to a task in the view is globally known to the software, and the software uses this information when it does resource allocation and scheduling.
By considering a free flowing and modifiable project hierarchy instead of a rigid single project structure, several other benefits are accrued. It becomes simple to roll up the same project in many different ways, as becomes necessary when the organizational structure changes. It becomes simple to group together several small projects and view them as part of a larger project.
Responsibilities
- Need analysis and user research interviews
- Defined the interaction model and designed views
- conducted user validation of wire frames
- Interacted with the development team to communicate wire-frames and decide technical trade-offs
- Reviewed development so that the final product confirms to UI guidelines
- Documented UI specifications – in terms of behaviour and look and feel.
Need analysis
Need analysis helped discover some underlying work practices regarding workflow management which needed to be addressed before any design activity could succeed.
User research
Conducted research interviews involving various roles like project manager, group leader, developer, team leader etc. to build a clear picture of real needs and issues of staff along with an understanding of the environment in which they work.
Included questions such as:
- What activities make up your job?
- What information do you need to do these activities?
- Where do you currently get this information?
- What other roles do you collaborate with?
This led to identification of tasks that are most critical to each role.
More over , tried to understand the existing system and the shortcomings of the system.
Defining the entity relationship model.
Attributes and tasks of each user-role
Wireframes – Interface views.
Members involved with the project can customize their view (dashboard), choosing from a list of pre–defined options and widgets. This allows each individual user to display the information they think is most important and in a way that fits their personal needs and work style.
