This paper delves further into the SEEWeb psychic by exploring the problems it solves, the technical mechanisms by which the problem is solved and how the SEEWeb is being employed to support real world projects. The problem is how to provide a widely diverse and geographically dispersed group of engineers, managers, and customers with accurate knowledge required to develop and evolve software, tailored to each user's unique perspective, and provided it in a cost effective manner. This problem is especially acute in stream-lined acquisition projects, where the Government is looking for less burdensome yet effective approaches to oversight. Traditional hard copy documentation and reporting practices are labor intensive, expensive and produce materials that are often outdated sometimes as they are even completed. Project area contains knowledge related to project management, such as, plans and schedules.
Process area shows the mechanism used to develop products.
Product area contains the collection customer required project outputs. Figure 1 represents the starting point for SEEWeb navigation. A user, with an engineering, management, or customer perspective, that has access to a browser, can dynamically obtain the latest and most accurate knowledge for a software project. The SEEWeb strives to present knowledge where existing SEEs provide information and CASE tools only provide data. A SEE with integrated tools might produce the additional information that there were 3426 requirements in the database last Friday and 14 requirements have been added in the last week.