Activity based development
The software development process in LN Studio is activity based. Before a software component can be modified, a software engineer must link the component to an activity. Each activity is part of a software project and each software project belongs to an Application.
This diagram shows an application, software projects, and activities:
A software application is a consistent set of packages that functionally belong together. An application is linked to a Base VRC, which determines the environment on the LN server in which the application's software components are stored. Administrators can create applications through the Application Explorer view.
See the Infor LN Studio Administration Guide.
For each high level software requirement (business requirement), a software project is created on the Project Server. Multiple projects can be defined per application. A software project is split up into activities. Project managers can create software projects and activities. They can also view the modified LN software components per activity, through the Software Project Explorer. A separate activity is created for each individual software requirement, such as a bug fix or a new feature within the project. Each activity is assigned to a software engineer. See "Defining a software project" in the Project Server documentation.
Software engineers can open their activities through the Activity Explorer view.
See Developing software components.
- Components in an activity
are only accessible for the software engineer to which the activity is
assigned. However, other software engineers can access these components if they
put this activity in the activity context of their own activity.
See Activity context.
- Activities can be shared over multiple software engineers when their names are added as Assignee in the Activity properties. In this case they also can modify the components.