JISC DEVELOPMENT PROGRAMMES
FINAL REPORT
Project
Project Acronym Grid API Project ID
Project Title An Authorisation API for the GRID
Start Date 1 March 2003 End Date Originally 28 Feb 2004
then altered to
30 September 2004 Lead Institution University of Salford
Project Director Professor David W Chadwick
Project Manager & contact details Professor David W Chadwick, email: d.w.Chadwick@https://www.doczj.com/doc/cb10339517.html, Tel: 077 9644 7184
Partner Institutions Officially None. Unofficially: Argonne National Laboratory, USA and the
University of Glasgow
Project Web URL https://www.doczj.com/doc/cb10339517.html,/
Programme Name (and
number)
None
Programme Manager Nicole Harris
Document
Document Title Final Report
Reporting Period
Author(s) & project role David Chadwick, Project Manager
Date 28 September 2004 Filename
URL https://www.doczj.com/doc/cb10339517.html,/Projects.htm#GridAPI
Access ? Project and JISC internal ? General dissemination Document History
Version Date Comments
0.9 24 Sept 2004 Pre-release to JISC and partners
1.0 28 Sept 2004 Final public release
Table of Contents Acknowledgements (2)
Executive Summary (3)
Background (4)
Aims and Objectives (4)
Methodology (4)
Implementation (5)
Outputs and Results (5)
Outcomes (6)
Conclusions (7)
Implications (7)
Recommendations (8)
References (8)
Appendix 1. Questionnaire for BRIDGES Scientists (9)
Appendix 2. Questionnaire for BRIDGES Implementers (10)
Acknowledgements
First and foremost, the author would like to thank the Globus Team, Argonne National Laboratory, and Von Welch in particular, for their co-operation and support throughout this project. Without their help it clearly would not have been possible to validate and test the implementation of the GRID Authorisation Interface between the Globus Toolkit and the PERMIS authorisation infrastructure. The Globus Team developed a new version of the Globus Toolkit, v3.3, specifically for this project.
The author would also like to thank Dr Richard Sinnott from the University of Glasgow, for volunteering to validate the implementation of the GRID Authorisation Interface in the BRIDGES project. Without this real life application environment to test the implementation, it would not have been possible to realistically determine if the GRID Authorisation Interface and PERMIS could provide the sort of additional useful authorisation functionality that Grid applications need.
The author would like to thank Chenghao Sun, MSc student at the University of Salford, who chose to study for his dissertation topic “The Usage of a New Role Based Privilege Management Infrastructure – PERMIS – in the BRIDGES Project”. This provided useful research results about the overall effectiveness of using an authorisation infrastructure such as PERMIS in a large scale scientific project such as BRIDGES. These results will be useful in guiding future work.
Finally, the author would like to thank JISC for funding this project. Without their support, this project could never have been undertaken in the first place.
Executive Summary
The objectives of this project were threefold.
- Firstly to work with security experts in the Global Grid Forum (GGF) to specify a standard Open Grid Services Architecture (OGSA) authorisation interface, based on the use of the
Security Assertion Markup Language (SAML), as a format for requesting and expressing
authorization assertions for Grid applications.
- Secondly to implement the specified SAML interface in the PERMIS authorisation system and the Globus Toolkit, and
- Thirdly to validate the implementation in a current Grid project, namely the BRIDGES project at Glasgow University.
Overall, the project has been extremely successful and has achieved more than its stated objectives. Clearly this project could not have been successful without the active collaboration of the Globus team at Argonne National Laboratory. They gave their verbal assurances, prior to the start of this project, that they would collaborate with us, and implement the final interface in Globus Toolkit. Full credit should be given to them for keeping to this verbal agreement, particularly given the turbulent times that followed the announcement of the migration of Globus Toolkit to web services and WSRF in January 2004. At one point it looked like the implementation in Globus Toolkit might not be produced, which would have severely jeopardised this project, but in the end it was produced just one month later than promised.
Development of the GGF draft specification took much longer than originally anticipated. This is often the case with standard’s development, since drafts have to be published for public scrutiny, and issues may arise that were not initially envisaged (in this case a revision of the SAML specification from V1.0 to V1.1). The version of the GGF draft that was implemented in PERMIS and GT3.3 was only finally published by the GGF in June 2004, several months after the implementations had been completed. It is anticipated that the final GGF specification will be published as a GGF standard sometime in 2005. Further, two new features, “action parameters” and “obligations” have been requested to be added to the interface. These features were not part of the original project specification and a new version of the authorisation interface will need to be produced within the GGF to take account of them.
Validation of the implementation in the BRIDGES project could not be quite completed before the close of this project, due to a delay in GT3.3 delivery and other factors. Nevertheless early results show that the addition of an interface to an external authorisation infrastructure such as PERMIS can provide much needed features to Grid applications such as BRIDGES. Studying how users and implementers actually used PERMIS and GT3.3 in BRIDGES also proved to be extremely useful in highlighting problems and issues that will need to be addressed in the future. These include: the need to dynamically change access control policies, the need to better educate users, and the need to standardise common roles for use by all VOs so that roles assigned by one member can be used to control access to the resources of another member.
In conclusion, this project has been extremely successful. It has specified an open standard authorisation interface that can be used by any Grid implementation and it has introduced significant extra functionality into Globus Toolkit v3.3 by coupling it to PERMIS via this interface. Finally, the project has revealed additional research and development work that will need to be undertaken in the future, including: specifying obligations, action parameters, and an interface for dynamically changing policies.
Background
The project arose from discussions and presentations at the Globus World Security Workshop in San Diego, 17 January, 2003. Globus Toolkit (GT) already supported a standard authentication infrastructure based on X.509 public key certificates, but did not have a standard authorisation infrastructure. In fact, the authorisation support provided by GT was very simple, based solely on name mappings in a Gridmap file. Several speakers had been invited to give presentations about their authorisation mechanisms. Mary Thompson from the Ernest Orlando Lawrence Berkeley National Laboratory gave a talk about Akenti [6]. The author gave a presentation about the PERMIS authorisation infrastructure [7] developed at the University of Salford under the EC PERMIS project. PERMIS provides strong role based access controls via standard X.509 attribute certificates.
After the presentations, Von Welch, the leader of security developments within Globus, suggested that an authorisation API design team be formed. He and colleagues had already produced an early GGF draft for a standard authorisation interface based on SAML v1.0 [1], and they needed to progress this within the GGF. The author agreed to join this team so that some European input could be added to, what was at that time, a purely US effort. It was also envisaged that the interface could be piloted and validated by a standards’ based authorisation infrastructure such as PERMIS.
On return to the UK, the author put a proposal to JISC for funding to help to develop the authorisation interface, and then to implement the interface in PERMIS [8]. JISC agreed to fund the proposal in two phases. Phase 1 was to produce the draft GGF specification, and Phase 2 would be to implement this in PERMIS, subject to satisfactory delivery of Phase 1.
Aims and Objectives
The objectives of this project were initially twofold.
- Phase 1. To work with security experts in the Global Grid Forum (GGF) to specify a standard Open Grid Services Architecture (OGSA) authorisation interface, based on the use of the
Security Assertion Markup Language (SAML) [1], as a format for requesting and expressing
authorization assertions for Grid applications.
- Phase 2. To validate and test the interface by implementing it in the PERMIS authorisation infrastructure.
JISC agreed to fund the above in two Phases. After Phase 1 was successfully completed, a new objective was informally added to Phase 2, this being:
- To validate the GT/PERMIS implementation in a current Grid project, namely the BRIDGES project at the University of Glasgow [9].
This last objective was an informal one, as no additional resources were provided to either Glasgow or Salford to perform the validation, and no contracts were exchanged. Nevertheless both parties fully intended to use their best efforts to perform the validation testing.
Methodology
The methodology used for Phase 1 was the typical methodology used by standards’ bodies, namely: update the existing (GGF) draft specification, submit it to review by the (GGF) working group, resolve any issues raised by the WG members, produce a revised version of the draft and continue in this vein until no additional issues are raised by the WG or consensus is reached, or time runs out. Note that this process is potentially unbounded, although most standards’ bodies usually have a timeline to work to.
The methodology used for Phase 2 was the standard waterfall systems development model. The final validation step was undertaken by the University of Glasgow, with Salford acting in an advisory and consultancy capacity. This entailed providing email and telephone support to Glasgow, and visiting Glasgow during September 2004 to help them overcome some of their difficulties.
Implementation
Phase 1 was planned so that each new versions of the GGF draft was available for download and comment by the GGF members prior to each GGF meeting. The author then attended the GGF meeting to present the latest version of the draft and to answer any questions and issues raised. In practice most of the editorial work was done by the author and by Von Welch. The work progressed according to the methodology. However, more cycles were performed than originally anticipated, and in fact, the cycle still has not quite finished. One of the reasons for the increase in cycles, was due to SAML v1.1 being published in September 2003 [2], which necessitated a significant change to the interface specification. Then during summer 2004 two things happened. Firstly validation testing by the University of Glasgow requested that an additional feature “action parameters” be added to the specification, and another GGF member requested that “obligations” be added to the interface specification. Although neither was within the scope of the current project, nevertheless they both provide useful features to be added to the interface specification. These issues were discussed at the GGF meeting in Brussels in September 2004, and it was agreed to freeze Version 1 of the interface in its current form with the existing features so that it can progress to GGF standard status, and to incorporate all new features in Version 2 that can be progressed separately.
Phase 2 was planned so that the implementation of the interface in PERMIS and GT3 would coincide as nearly as possible. The target date for completion was the beginning of April 2004. The implementation by Salford went according to plan. However, the planned implementation by the Globus team suffered a severe setback when it was announced in January 2004 that GT would move to web services and WSRF. Initially it looked like the planned implementation of the authorisation interface may be postponed indefinitely. However, after two months things stabilised somewhat at Argonne, and the importance of the authorisation interface work was recognised by the Globus management. The interface was duly implemented just one month after its original target date and was made available May 2004.
Concerning the implementation at Salford, adding SAML to PERMIS using OpenSAML was not too complex. However, the complexity of implementing PERMIS as a Globus web service was underestimated, due to the volume of web services and Globus documentation that needed to be understood prior to implementation. Furthermore, the time difference between the geographical locations of Salford and Chicago caused significant delays in responses to our support requests. Fortunately the developer, Dr Sassa Otenko, was outstanding, and he managed to finish the implementation on time.
Validation of the GT3.3/PERMIS implementation by the University of Glasgow had to start late due to the late delivery of GT3.3 by the Globus team. It was also further delayed due to the summer vacations and the honeymoon of the main Salford developer (Dr Otenko). Furthermore, the Globus team did not publish GT3.3 on their normal download page under latest releases, but rather on a (partially hidden) research/experimental page. Consequently the implementer at Glasgow downloaded the latest published GT release (which actually did not have the authorisation interface in it) and then wasted considerable time trying to get this to interwork with PERMIS, which of course it was unable to do. It was only after Salford staff visited Glasgow in September 2004 that this problem was recognised and that proper interworking tests could start. Consequently they were not finished by the time this report was written. Nevertheless some valuable results were still obtained in time for this report. It is also worth noting that the University of Glasgow are exploring this Grid API within the JISC funded DyVOSE project [11].
Finally, an additional piece of research was carried out by Chenghao Sun from the MSc in Managing IT degree at the University of Salford. The aim was determine how usable the combined
GT3.3/PERMIS implementation is within the BRIDGES project and to present his finding in his MSc dissertation [4]. This necessitated him producing questionnaires for BRIDGES users and implementers (see Appendices 1 and 2), then interviewing them and analysing the results. Outputs and Results
The first significant output of the project is the publication of the GGF authorisation interface [3]. This interface is likely to become widely accepted in the Grid community, as different researchers start to
implement it. We are already aware of 4 groups of researchers who are at various stages of implementation. It is anticipated that this will become a final Grid specification in 2005.
The second significant output is the implementation of the interface in Globus Toolkit v3.3 and in the PERMIS authorisation infrastructure, providing Globus with its first plug and play comprehensive authorisation system. Both the GT3.3 and PERMIS implementations have been distributed worldwide via the US NMI release.
The third output is the presentation of a paper describing the SAML implementation in GT3.3/PERMIS at the IFIP CMS2004 conference in Windermere, September 2004 [10].
The fourth (indirect) output of this project will be a report from the BRIDGES project describing their experiences of using the combined GT3.3/PERMIS implementation. This was described in outline in [12] however a more detailed exploration of this interface usage is to be documented in the upcoming BRIDGES project deliverables.
The fifth (indirect) output of this project is a prototype standalone SAML enabled PERMIS Authorization Decision Engine, which allows the use of PERMIS Authorization separately from GT3.3. It receives SAML Authorisation Decision Queries and responds with SAML Authorisation Decision Statements, as defined by the GGF standard. The standalone PERMIS Authorisation Decision Engine could be used in one of the Shibboleth-PERMIS integration scenarios, whereby a number of protected Apache Web-servers could contact a central PERMIS Authorisation Decision Engine for access control decisions.
The sixth (indirect) output of this project will be the MSc dissertation [4] which provides an objective view of how a role based access control system such as PERMIS can be used by users and implementers in the BRIDGES project. This dissertation has already highlighted areas where future work will be needed in this space, regardless of which technology is actually used. This includes: education of end users to understand what security mechanisms are available to them and how they can best be used by them to protect their data; standardisation of a set of common attributes and values that can be used universally by VO members, regardless of the VO they are in; and an ability to quickly and easily dynamically change access control policies as VO roles and shared data sources change within the scientific experiments. One other finding was the mismatch between user expectations and technology capabilities. One (Some??) user thought that individual database columns should have separate policies protecting them, but given that a project like BRIDGES has potentially millions of database columns, this could not be enacted using the current PERMIS infrastructure.
Outcomes
In some ways the project has exceeded the original objectives set for it, and in other ways it has fallen somewhat short. Taking the latter first, it was originally anticipated that the GGF authorisation interface specification would have been finished and published as a GGF standard by the end of this project. This has not happened due to several reasons. Firstly the wheels of the GGF standards making process ground more slowly than originally anticipated, secondly, the underlying OASIS standard on which the work was based changed versions midway through, and thirdly, interest in the work (which is a good thing) meant that additional features outside the scope of the original project, were requested by some GGF participants. The net result of this is that version 1 of the interface specification will only finish progressing through the GGF during 2005, and that a second version now needs to be developed to take account of the new requirements. This in itself is not a bad thing, if it means that more people will want to implement the specification because it contains features that they require.
There was a slight shortfall in the informal objective to validate the authorisation interface in the BRIDGES project. This was caused by the delay in producing GT3.3, which caused a delay in the BRIDGES project being able to complete its integration validation testing before the end of this project. However we expect that this shortfall will eventually be rectified when BRIDGES produces its final report.
The ways in which this project has exceeded its original objectives are as follows:
- Firstly the PERMIS implementation can now be called by GT3.3 as either an internal authorisation decision handler or as a standard Grid service via SAML. Only the latter was
originally proposed.
- Secondly, the PERMIS implementation can now run as a standard SAML Authorisation Decision Engine as well as a standard Grid service. Only the latter was originally proposed.
- Finally, additional research was carried out by Chenghao Sun, MSc student, into the usability of an integrated GT/PERMIS system. This has given valuable insights into the sorts of
problems and issues that still need to be addressed when providing a sophisticated access
control interface to a complex Grid application such as BRIDGES, regardless of the
technology actually being used.
Conclusions
In conclusion, the project has been very valuable. It has allowed a standard authorisation interface for Grids to be specified and standardised within the GGF, which will allow Grid applications to seamlessly mix and match authorisation infrastructures with Grid co-ordinating software such as Globus Toolkit. It has shown that the interface works and can provide a basic authorisation service to Grid applications. Finally, it has shown were further work is needed in the future, both in educating users and in making policy based authorisation software more scalable and dynamically changeable. Implications
The multimillion-euro EGEE project intends to implement the authorisation interface developed by this project in their Grid infrastructure. Once it has this interface, the EGEE project should seriously consider using the PERMIS authorisation infrastructure instead of or as well as VOMS. PERMIS already provides many more sophisticated features than VOMS including comprehensive policy driven decision making, support for push and pull modes, and static delegation of authority. It will shortly provide even more features such as static and dynamic separation of duties and dynamic delegation of authority. Since the UK is investing heavily in PERMIS development, it ought to capitalise on this investment in the EGEE project for the benefit of its European partners.
Additional features have been requested to be added to the current interface specification. “Action parameters”, requested by the University of Glasgow, and “obligations”, requested by the US Primea developers, are two such features. This means that further work will be needed to enhance version 1 of the interface specification (the author has already produced a straw man revised version containing obligations which was presented to the GGF meeting in Brussels, September 2004).
The PERMIS implementation currently supports the passing of action parameters, but neither the SAML interface nor Globus Toolkit support this. Work will be needed to add this once the GGF specification has been agreed upon.
The PERMIS implementation currently does not support obligations. Work will be needed to add this feature to PERMIS and to the SAML interface once it is standardised within the GGF. Note however that the most difficult work in supporting obligations is not within the authorisation infrastructure or the SAML interface, but rather is within the obligation enforcement function that will need to enact the obligations that are passed to it.
SAMLv2.0 is expected to be released shortly. At the time of writing it is at Committee Draft stage. The implication here is that maintenance work will be needed on version 1 of the interface specification to allow it to migrate to SAMLv2.0.
The BRIDGES project found that new access control policies need to be dynamically created and invoked as new roles and new data sources are added to the scientific experiments. There has been informal discussion within the GGF for a new management interface specification to be developed that will allow commands to be sent to a Policy Decision Point (such as in PERMIS) telling it to change its policy. It would be useful to define such a protocol in the GGF and to implement it in PERMIS.
An unanticipated spin off from this project is a standard SAML supporting stand alone PERMIS authorisation decision engine (as opposed to a Grid service one). Such a stand alone engine can be
used by other SAML supporting mechanisms such as Shibboleth and Liberty Alliance. This may be of value to the academic community, say, by providing a centralised authorisation service.
Note that this interface is different to the deliverables of the JISC SIPS project, which is providing an integrated Shibboleth-PERMIS implementation rather than a stand alone one.
Recommendations
The author recommends that other Grid projects that need a flexible role based access control scheme should consider using the combined GT3.3/PERMIS implementation.
References
[1] OASIS. “Assertions and Protocol for the OASIS Security Assertion Markup Language (SAML)”. 19 April 2002. See https://www.doczj.com/doc/cb10339517.html,/committees/security/
[2] OASIS. “Assertions and Protocol for the OASIS Security Assertion Markup Language (SAML)
V1.1”, 2 September 2003
[3] Von Welch, Frank Siebenlist, David Chadwick, Sam Meder, Laura Pearlman. “Use of SAML for OGSA Authorization”, June 2004, Available from https://https://www.doczj.com/doc/cb10339517.html,/projects/ogsa-authz [4] Chenghao Sun “The Usage of a New Role Based Privilege Management Infrastructure PERMIS in the BRIDGES Project”, MSc dissertation, University of Salford, to be submitted October 2004
[5] Von Welch, Frank Siebenlist, David Chadwick, Sam Meder, Laura Pearlman. “Use of SAML for OGSA Authorization”, Sept 2004, Available from https://https://www.doczj.com/doc/cb10339517.html,/projects/ogsa-authz [6] Johnston, W., Mudumbai, S., Thompson, M. “Authorization and Attribute Certificates for Widely Distributed Access Control,” IEEE 7th Int Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE), Stanford, CA. June, 1998. Page(s): 340 -345 (see also
https://www.doczj.com/doc/cb10339517.html,/security/Akenti/)
[7] D.W.Chadwick, A. Otenko, E.Ball. “Role-based access control with X.509 attribute certificates”, IEEE Internet Computing, March-April 2003, pp. 62-69.
[8] D.W.Chadwick. “CASE for SUPPORT. An Authorisation API for the GRID”. February 2003
[9] R.O. Sinnott, D. Gilbert, D. Berry, E. Hunt, M. Atkinson, BRIDGES: Security Focused Integration of Distributed Biomedical Data, Proceedings of the UK e-Science All Hands Meeting, Nottingham, September 2003.(https://www.doczj.com/doc/cb10339517.html,/projects/bridges).
[10] David W Chadwick, Sassa Otenko, Von Welch. “Using SAML to link the GLOBUS toolkit to the PERMIS authorisation infrastructure”. Proceedings of Eighth Annual IFIP TC-6 TC-11 Conference on Communications and Multimedia Security, Windermere, UK, 15-18 September 2004
[11] Dynamic Virtual Organisations for e-Science Education,
https://www.doczj.com/doc/cb10339517.html,/index.cfm?name=project_dyvose&src=alpha
[12] R.O. Sinnott, D.W. Chadwick, Experiences of using the GGF SAML Authz interface, Proceedings of the UK e-Science All Hands Meeting, Nottingham, September 2004.
Appendix 1. Questionnaire for BRIDGES Scientists
Place: Time:
Name of Interviewee: Position in the BRIDGES project:
Hello, my name is Chenghao Sun, and I am currently an MSc student at the University of Salford. I am doing some research on the security requirement of the BRIDGES project and wondered if you could spare around 20 minutes to complete this questionnaire.
Q1. What data are you sharing via the Bridges system? Could you generally describe the significance of the data?
Q2. a) Do you want to share your data in the BRIDGES system with others?
?Yes, some of my data ?Yes, all of my data ?No
b) If yes, who is sharing your data with you?
c) Who is allowed to modify, delete or add to the data?
Q3. How do you classify the security level of your data? (For example, public data that can be shared by all users in the system, semi-public data that can be accessed by some partners, etc)
Q4. a) Do you think that scientists using BRIDGES system should be divided into groups (e.g. based on their roles or departments) that have different rights to access the data in the system?
?Yes ?No ?I don’t know
b) If so, how many roles/groups are needed to be classified to access your data? What are they?
c) If not, how do you decide who can access the data (e.g. is it by named individuals). (If this is
the case then go next to Q12)
Q5. What permission should be set for each role/group? (e.g. read, update, add or delete some data) Q6.Are there any hierarchical relationships between these roles/groups? (Such as manager and normal staff, the manager should have all the rights of normal staff) If YES, please write
comment.
Q7. Are there mutual exclusion relationships (such as purchasing manager and accounts payable manager, the same person not permitted to belong to both roles) between the roles/groups? If YES, what are they?
Q8. Do you think the system will grow large in the future for example lots of new users or some other research sites will get involved? ?Yes ?No ?I don’t know
Q9. In your opinion, how fine-grained should be the permission of access granted to users?
?Access to a whole DB server ? Access to DB tables
? Access to individual DB fields or rows ?Access to DB columns
? other measures to divide information targets
Q10.Before the introduction of the BRIDGES system did extend scientists get access to your data? If so was this based on their roles? ?Yes (Go to Q11) ?No (Go to Q12) ?I don’t know
Q11. Do you think it is easy to assign the roles and their permissions?
?Yes ?No why
?I don’t know
Q12. Do you know what access policy was used by your site before PERMIS was used? If YES, please describe it.
THANK YOU FOR YOUR ASSISTANCE!
Appendix 2. Questionnaire for BRIDGES Implementers Place: Time:
Name of Interviewee: Position in the BRIDGES project:
Hello, my name is Chenghao Sun, and I am currently an MSc student at the University of Salford. I am doing some research on the usability of the PERMIS system in the BRIDGES project and wondered if you could spare around 20 minutes to answer a few questions.
1. Generally, how good do you think the PERMIS system is as an authorization infrastructure for
the BRIDGES project?
?Very good ? Good ?Acceptable ? Inappropriate
2. Please briefly describe the configuration that you have adopted (LDAP, GGF Authz, SAML
interface?, Java API? Etc.)
3. How did you find the PERMIS cookbooks and documentation?
4. Could you please suggest any improvements that should be made to the cookbooks and
documentation?
5. What was your role in the application of the PERMIS infrastructure?
6. Would you like to list the tasks that you have undertaken so far during the application of the
PERMIS infrastructure?
7. Would you like to list the tasks that you still have to undertake during the application of the
PERMIS infrastructure
8. From your experience, do you think the integration project with the PERMIS system is time
consuming?
?Yes, I waste lots of time ? Yes, but just a little bit more than I imaged
?No, It is ok ? No, it is quite easy and convenient
9. How much time have you spent on the PERMIS aspect of your project so far (in hours)? Do
you think it is time consuming?
10. How much time do you think it will take in total (in hours)
11. If you used the Policy Management Graphical User Interface for constructing PERMIS
policies please answer the following questions:
i. How much do you like the tool (on a scale from 1 (very poor) to 10 (very
good)
ii. Was it quick and easy to learn to use (on a scale from 1 (very slow/difficult) to
10 (very good/fast/easy)
iii. Did it allow you to produce the policy you needed ?Yes ?No
iv. What did you not like about the tool
v. What did you like about the tool
vi. Do you have any suggestions for improvements
12. To what extent do you need to change the local authorization policy during the integration?
?totally ?a large part ?a small part ? none
If there is any changes, could you describe them
13. What tool did you use to create X.509 Attribute Certificates for the users.
14. How did you like it (on a scale from 1 (very poor) to 10 (very good) )?
15. Have you any suggestions for improvements?
16. How do you think the PERMIS system will fit your scalability requirements?
?Very good ? Good ?Acceptable ? Bad
17. What problems were identified during application of the PERMIS infrastructure?
18. Could you fix the problems by yourself easily?
?Yes, mostly it is ?Yes, but in several times it is quite hard ? No
19. Was it easy to get support to fix the difficult problems?
?Yes, it is easy to contact with the PERMIS project team and the documents are sufficient ?No, it is easy to contact with the PERMIS project team but the documents are not enough
?No, it is hard to contact with the PERMIS project team.
20. Was there any functionality missing that you expected?
21. Do you know what is the deadline of the BRIDGES project?
?Yes MM DD YY
?No
THANK YOU FOR YOUR ASSISTANCE!
招聘网站设计项目详细设计 第一部分、引言 1.1编写目的 本说明在概要设计的基础上，对招聘网站设计项目的各模块、页面、脚本分别进行了实现层面上的要求和说明。 软件开发小组的产品实现成员应该阅读和参考本说明进行代码的编写、测试。 1.2背景 说明： A、软件系统的名称：招聘网站设计项目 B、任务提出者：668Job在线科技发展有限公司 开发者：北大青鸟Aptech产品开发部 本项目将实现668Job的原型部分，并且在该原型的基础上进行功能的扩展和需求的界定，最终完成的版本将在https://www.doczj.com/doc/cb10339517.html,网站上使用。提供互联网上的求职、招聘登记和搜索服务。 C、本系统将存储用户信息，668Job将与其他的系统共享这些注册信息，共享的系统可能是 668Job电子邮件系统、668Job电子杂志分发系统。 这些系统之间不提供应用程序级别的接口，数据共享通过SQL Server数据库表的公共访问来实现。 本系统将使用SQL Server 2000作为数据库存储系统，SQL Server 2000企业版将由668Job自行购买。 1.3定义 IPO图——输入/处理/输出图，一般用来描述一个程序的功能和机制；
1.4参考资料 相关的文件包括： A、湖人诊所的内部文件《核准招聘网站设计项目》； B、《招聘网站设计项目需求说明》； C、《招聘网站设计项目项目开发计划》； D、《招聘网站设计项目概要设计》； 参考资料： A、北大青鸟Aptech ACCP3.0 Sem2《基于软件开发项目的毕业设计》； B、北大青鸟Aptech ACCP3.0 Sem2《ASP程序设计》； C、国家标准《详细设计说明书（GB8567——88）》； D、莱克公司的人力资源管理项目的详细设计说明； 合同： A、《招聘网站设计项目合同20031102 - 54》； （说明：不同的文档都有第一部分类似的引言部分，这样是为了文档能够在独立使用的时候，能够提供足够的背景信息。）
高中英语学习材料 madeofjingetieji 盐城市龙冈中学牛津高中英语模块一测试题 命题人：程永华 第一卷(选择题，共75分) I.听力（共两节，满分20分） 第一节（共5小题；满分5分） 听下面5段对话。每段对话后有一个小题，从题中所给的A、B、C三个选项中选出最佳选项，并标在试卷的相应位置。听完每段对话后，你都有10秒钟的时间来回答有关小题和阅读下一小题。每段对话仅读一遍。 1.How much is the skirt? A.$19.15. B.$9.15. C.$9.50 2.What are the two speakers doing? A.They are having a rest. B.They want to have dinner. C.They are hiking on a hill. 3.What does the man mean? A.He doesn't like Chinese food. B.He doesn't want to eat out. C.He wants to pay for the meal. 4.What did the man do yesterday evening? A.He had dinner with his friend. B.He visited a friend. C.He saw a film. 5.When does Mr Brown have to be at the airport? A.At 8:30. B.At 9:30. C.At 10:30. 第二节（共15小题，满分15分） 听下面5段对话或独白。每段对话或独白后有几个小题，从题中所给的A、B、C三个选项中选出最佳选项，并标在试卷的相应位置。听每段对话或独白前，你将有时间阅读各个小题，每小题5秒钟；听完后，各小题将给出5秒钟的作答时间。每段对话或独白读两遍。 听第6段材料，回答第6至8题。 6.What kind of color TV does the woman want to buy? A.A small one. B.A big one. C.A cheap one. 7.What's the man's opinion about buying a TV? A.The woman should buy a small one. B.The woman should buy a big one. C.The woman should buy a cheap one. 8.Why does the man give the woman such a suggestion? A.Because the big one is too expensive. B.Because she will have to change it in a few years. C.Because her sitting room isn't very big. 听第7段材料，回答第9至11题。 9.Where is the boy going to spend his holiday? A.In the city. B.In his hometown. C.Abroad. 10.What will he do there? A.Do some farm work. B.Study at home. C.Do some housework. 11.Which of the following is TRUE? A.The girl knows how to farm. B.The boy's grandparents don't live in the city. C.The boy's school is in the country. 听第8段材料，回答第12至14题。 12.What are the man and the woman looking for? A.A comfortable hotel. B.A modern hotel. C.A cheap hotel. 13.Where could the man and the woman find the hotel they need? A.Next to the bank. B.A two minutes' drive to the west. C.On the left side of the street.
储蓄业务项目管理计划书 1．简介 项目概述 本项目要开发一个银行系统，系统一共分为储蓄业务、贷款业务、外汇交易、网上银行、信用卡业务和系统管理六个子系统。本团队负责其中的有关储蓄业务 的子系统。通过团队合作开发整个子系统，使团队成员获得软件工程开发的实际训练。本系统采用目前主流的B/S开发架构，将与整个银行系统一起发布。不单独发布。交付的产品包括可执行的文件、源代码、技术文档与用户使用手册等。本系统的开发过程中的主要工作是子系统需求分析、系统总体设计、子系统源代码开发、子系统测试、交付团长进行最后的集成、整个系统的测试。关键里程碑是制定项目管理计划书、制定需求设计规格说明书初稿、制定系统设计报告的初稿、进行子系统运行情况的检查与测试、进行系统集成后的运行情况的检查与测试。项目所需工具是个人电脑和开发工具。进度为11周，工程量为3人/天。 项目范围说明 （1）提交文档：项目管理计划、需求规格说明，设计报告、测试报告、用户使用手册和项目个人总结。其中项目总结为每人一份，每个小组所有成员的总结装订在一起；其余文档每组提交一份。每个团队可将各小组的文档综合到一起，各小组也可自行分开提交，具体方式由团队内部协商确定。所有文档需要提交电子版和打印稿。 （2）源程序检查：一共两次。第一次检查每个小组的子系统运行情况。第二次检查每个团队内六个小组集成后完整的银行系统运行情况，检查完成后需要提交程序源文件和可执行的系统。程序检查安排在上机时间进行。 软件项目计划书的演化 软件项目计划书在第三周周末前经由小组讨论、共同撰写、汇总整合三步骤形成初稿，第四周以后根据项目的进展可以对其进行修改，需要有组员提出修改意，在全体会上讨论通过，并由组长整理修改意见并作出相应的修改。其余组员同步获得更新稿。 2．项目组织管理 过程模型 表1.过程模型表 团队的分工与合作
选修六 Unit 1 1.adj. 现实主义的；逼真的；现实的 2.adj. 抽象的；深奥的n. 摘要 3.n. 雕塑 4.n. 雕刻家；雕塑家 5.n. 美术陈列室；画廊 6.n. 信任；信心；信念 7.adv. 忠实地 8.adv. 所以；因而 9.n. 目标；目的vi. & vt. 瞄准；（向某方向）努力 10.adj. 常规的；传统的；因循守旧的 11.adj. 典型的；有代表性的 12.adj. 明显的；明白的 13.n. 新生；复兴；复活 14.vt. 采用；采纳；收养 15.adj. 人道主义的 16.vt. 拥有；具有；支配 17.n. （尤作复数）所有；财产 18.adj. 卓越的；杰出的；极好的 19.n. 透视画法；透视图；观点 20.n. 技术；方法；技能 21.n. 巧合（的事）；（事情、口味、故事等）相合 22.巧合地 23.n. 杰作；名著 24.n. 印象主义；印象派 25.adj. 印象派的 n.印象派艺术家 26.adj. 后印象派的n. 后印象派艺术家 27.大量28.n. 阴影；影子 29.adj. 荒谬的；可笑的 30.adj. 争论的；争议的 31.n. 努力；尝试；企图vt. 尝试；企图 32.（可是）另一方面 33.vt. 预言；预告；预测 34.n. 风景；景色 35.adj. 确切的；特定的 36.n. 画像；身材；数字 37.n. 黏土 38.n. 评论家；批评者 39.n. 青铜；青铜色；青铜制艺术品 40.n. 大理石 41.vt. 雕刻；刻记 42.adj. 脆弱的；容易生病的；精致的 43.n. 帆布；画布 44.n. 咖啡馆；小餐馆 45.adj. 过敏性的；对……过敏的 46.adv. 有效地 47.n. 展览；陈列；展览会 48.adj.敢做敢为的;侵略的；好斗的 49.n. 学者 50.n. 肉；肌肉；肉体 51.活着的；本人 52.n. 几何学 53.n. 束；串 54.n. 林荫道；道路；大街 55.n. 喜爱；偏爱
学软件开发，找软件工程师培训学校，北京哪家较好？学软件开发已经受到了广大初高中毕业生的青睐，作为北京地区的学生，选择在哪个学校学习软件开发已经成为广大考生迷惑的问题。而众所周知的北大青鸟软件开发课程是最好的，自然学软件开发去北京北大青鸟佳音校区！ 20世纪90年代以来，全球软件行业作为新兴产业，每年以平均13%的发展速度增长，中国处于价值链低端，产业态需要，国际软件行业的发展，迫使中国软件产品发展迫在眉睫。我国软件产品的整体技术含量和价值含量都比较低，需要培养高素质软件开发人员。国际化产业的需求，国家人才的缺乏导致软件开发成为近年来年较热门的IT专业。 那么我们为什么要选择北京北大青鸟佳音校区软件开发专业呢？其优势如下： 第一、课程系统，全面 北京北大青鸟佳音校区提供的不是单科的培训，而是系统的，全面的软件开发技术的培训，所有课程结构循序渐进。 第二、课程轻重分明 本课程重点是培养Java高级工程师和.net高级工程师，北京北大青鸟佳音校区的宗旨是“让学精一门语言，然后培养学生融会贯通的思想，学活其他语言”，因为软件的发展日新月异，学生只有学
活了程序设计语言，毕业后才能适应软件开发工作，才能在这领域里有所突破。 第三、采用“产学元方式教学” 北京北大青鸟佳音校区在平常的教学过程中，尽可能的将教学内容和企业发展相结合，学生时常可以去企业实践、用课本上的知识来为企业服务，用企业的先进技术带动学校的发展。真正做到学有所长、学有所用。 第四、培养扎实的理论基础 北京北大青鸟佳音校区不仅提供专业编程知识，同时，为了锻炼学生逻辑思维，还设置其他相应课程，比如：高数等，为了让学生全面掌握计算机软件，我们还开设了数据结构、操作系统等课程，为学生的进一步的学习。 第五、实践性强，针对性强 北京北大青鸟佳音校区的课程是与企业完全同步的，每个实践例子都是经过行业专家长期研讨开发出来的，因此在内容组织上，授课方式上都有成熟而先进的经验，确保学员“能够学会”，“学会了能够就业”。 第六、我们重视理论+实践，也注重职业素养的培养。 北京北大青鸟佳音校区的课程关注企业所注重的职业素养的培训，在班级管理，就业训练上都有专门的人员进行负责，保证项目经
高一英语期中复习基础题选编（1） Ⅰ.语法填空 1．Bill’s mother was always telling him of the dos and don'ts，but it didn’t ________. A．use B．work C．stop D．promise 2．He was obviously annoyed，for he was not used to ________ like that. A．speaking B．spoken to C．being spoken D．being spoken to 3．Zhang Hua is clever and works hard at his lessons.________. A．So is Li Ming B．So does Li Ming C．It was the same with Li Ming D．So it is with Li Ming 4．I must have been a great________to my parents in those hard days，for I never failed to live up to their expectations. A．achievement B．comfort C．disappointment D．support 5．Good amounts of sleep every night ________also important for your health. A．is B．are C．was D．were 6．Even if I had taken part in the 400－meter relay race in the sports meet，our class________ the race.I’m ________ weight this year. A．would not have beaten；putting on B．might not have won；gaining C．cannot have defended our title；losing D．must not have achieved；acquiring 7．Teenagers ________ their health because they play computer games too much. A．have damaged B．are damaging C．damaged D．will damage 8．What you told me the other day is really true，________？ A．isn’t it B．isn’t what C．didn’t you D．wasn’t it 9．In the amusement parks，all the people love their jobs，________ might be not popular but are quite interesting regardless. A．which B．what C．that D．where 10．—Alice，you feed the bird today，________？ —But I fed it just now. A．do you B．will you C．don’t you D．didn’t you 11．In the past few years，My Heart Will Go On was a popular song among young people，________ were often heard singing it at parties. A．who B．which C．they D．that 12．________ is known to all，he is admitted to a key university. A．It B．What C．Which D．As 13．—Most of my classmates failed in the first exam.It seems there is no hope for us to make any progress.
软件项目管理计划书 项目名称： 时间：年月日
目录 1.简介 (3) 1.1.项目概述 (3) 1.2.项目主要功能及性能 (3) 1.3.项目交付产品 (3) 1.4.参考资料 (3) 2.项目组织 (3) 2.1.过程模型 (3) 2.2.团队的分工与合作 (4) 3.管理过程 (4) 3.1.管理目标及优先级 (4) 3.2.风险管理 (5) 3.3.监督及控制机制 (5) 3.4.人员计划 (5) 3.5.培训计划 (6) 3.6.风险管理计划 (6) 3.7.项目配置计划 (7) 3.8.计划更新策略 (7) 3.9.项目沟通计划 (8) 3.9.1.项目组会议 (8) 3.9.2.项目报告机制 (8) 3.10.项目的重用计划 (9) 3.11.质量保证活动 (9) 3.11.1.内部审核 (9) 3.11.2.阶段审核 (10) 4.技术过程 (10) 4.1.开发工具、方法和技术 (10) 4.2.软件需交付的文档 (10) 5.开发进度安排及预算 (11) 5.1.进度表格描述 (11) 5.2.开发过程中的资源需求 (11) 5.3.软件管理过程中预算及资源分配 (12) 5.4.项目进度及关键工期设置 (12)
1.简介 1.1.项目概述 1.2.项目主要功能及性能 1.3.项目交付产品 （1）提交文档：项目管理计划、需求规格说明，设计报告、测试报告、用户使用手册和项目个人总结。其中项目总结为每人一份，每个小组所有成员的总结装订在一起；其余文档每组提交一份。每个团队可将各小组的文档综合到一起，各小组也可自行分开提交，具体方式由团队内部协商确定。所有文档需要提交电子版和打印稿。 （2）源程序检查：一共 1.4.参考资料 2.项目组织 2.1.过程模型
人教版新课标高中英语选修7课文原文 Unit 1 Living well-Reading MARTY’S STORY Hi, my name is Marry Fielding and I guess you could say that I am "one in a million". In other words, there are not many people like me. You see, I have a muscle disease which makes me very weak, so I can't run or climb stairs as quickly as other people. In addition, sometimes I am very clumsy and drop things or bump into furniture. Unfortunately, the doctors don't know how to make me better, but I am very outgoing and have learned to adapt to my disability. My motto is: live One day at a time. Until I was ten years old I was the same as everyone else. I used to climb trees, swim and play football. In fact, I used to dream about playing professional football and possibly representing my country in the World Cup. Then I started to get weaker and weaker, until I could only enjoy football from a bench at the stadium. In the end I went into hospital for medical tests. I stayed there for nearly three months. I think I had at least a billion tests, including one in which they cut out a piece of muscle from my leg and looked at it under a microscope. Even after all that, no one could give my disease a name and it is difficult to know what the future holds. One problem is that I don't look any different from other people. So sometimes some children in my primary school would laugh, when I got out of breath after running a short way or had to stop and rest halfway up the stairs. Sometimes, too, I was too weak to go to school so my education suffered. Every time I returned after an absence, I felt stupid because I was behind the others. My life is a lot easier at high school because my fellow students have accepted me. The few who cannot see the real person inside my body do not make me annoyed, and I just ignore them. All in all I have a good life. I am happy to have found many things I can do, like writing and computer programming. My ambition is to work for a firm that develops computer software when I grow up. Last year invented a computer football game and a big company has decided to buy it from me. I have a very busy life with no time to sit around feeling sorry for myself. As well as going to the movies and football matches with my friends, I spend a lot of time with my pets. I have two rabbits, a parrot, a tank full of fish and a tortoise. To look after my pets properly takes a lot of time but I find it worthwhile. I also have to do a lot of work, especially if I have been away for a while. In many ways my disability has helped me grow stronger psychologically and become more independent. I have to work hard to live a normal life but it has been worth it. If I had a chance to say one thing to healthy children, it would be this: having a disability does not mean your life is not satisfying. So don't feel sorry for the disabled or make fun of them, and don't ignore them either. Just accept them for who they are, and give them encouragement to live as
第一讲定语从句 一关键词 定语从句：在复合句中修饰某一名词或代词的从句叫定语从句。一般紧跟在它所修饰的先行词之后。 先行词：定语从句所修饰的词叫先行词。 关系词：关系词用来引导定语从句。关系词有关系代词和关系副词之分。关系代词有that, which, who，whom，whose，as等；关系副词有when，where，why等。 关系词可以1) 代替先行词；2) 引导定语从句；3)在定语从句中担当一个成分。 例如：The car which my uncle had just bought was destroyed in the earthquake.句中，the car 为先行词；which是关系词引导是定语从句which my uncle had just bought，同时代替先行词the car在定语从句中作主语。 1.关系代词引导的定语从句 who指人，在定语从句中作主语。 whom指人，在定语从句中作宾语，常可省略。 which指物，在定语从句中做主语或宾语，做宾语时可省略。 that指人时，相当于who或whom；指物时，相当于which。在定语从句中作主语或宾语，作宾语时可省略。 whose 通常指人，有时也可指物，在定语从句中做定语。 Note: whose指物时，常用of which结构来代替： 关系代词在定语从句中作主语时，谓语动词要和先行词的性、数保持一致。 注意：which和as引导非限制性定语从句时，有时并没有特定的先行词，而是代表前面说的整个情况。这时which和as 被看作单数，译作“这一点”，其后的谓语动形式用单数形式。如：He said he was a Frenchman，which／as was not true. 但须注意，as引导的这种定语从句可置于主句之前，which引导的这种定语从句只置于主句之后。如：As is known to all，China is a socialist country. China is a socialist country, as/which is known to all. 2.关系副词引导的定语从句 when指时间，在定语从句中作时间状语。 where指地点，在定语从句中作地点状语。 why指原因，在定语从句中作原因状语。 注意：关系副词引导的定语从句经常可以用“介词+关系代词”引导的定语从句来表示。 介词+关系代词 1)根据动词选择介词。I don't know the foreigner with whom my teacher shook hands.（或I don't know the foreigner whom my teacher shook hands with.) Note: who和that不能直接位于介词后作宾语；有的短语动词是不能拆开的，常见的这类短语有：look for，look after等。
选修7 Unit 1 1.disability n. __________ 2.disabled adj. __________ 3.hearing n. __________ 4.eyesight n. __________ 5.△syndrome n. __________ 6.△infantile paralysis __________ 7.△Rosalyn n. __________ https://www.doczj.com/doc/cb10339517.html,p n. __________ 9.ambition n. __________ 10.ambitious adj. __________ 11.dictation n. __________ 12.△Sally n. __________ 13.noisy n. __________ 14.suitable adj. __________ 15.entry n. __________ 16.beneficial adj. __________ 17.△Marty __________ 18.in other words __________ 19.clumsy adj. __________ 20.△bump vi. __________ 21.outgoing adj. __________ 22.adapt vt. __________ 23.adapt to __________ 24.bench n. __________ 25.cut out __________ 26.microscope n. __________ 27.out of breath __________ 28.absence n. __________ 29.fellow adj. n. __________ 30.annoy vt. __________ 31.annoyed adj. __________ 32.△annoyance n. __________ 33.all in all __________ 34.firm n. adj. __________ 35.software n. __________ 36.sit around __________ 37.as well as __________ 38.parrot n. __________ 39.tank n. __________ 40.tortoise n. __________ 41.in many ways __________ 42.psychology n. __________ 43.psychologically adv __________ 44.make fun of __________ 45.encouragement n. __________ 46.conduct n. vt. __________ 47.△mainstream n. __________ 48.△fulfilling adj. __________ 49.never mind __________ 50.politics n. __________ 51.abolish vt. __________ 52.△abolition n. __________ 53.resign vi. & vt __________ 54.slavery n. __________ 55.literature n. __________ 56.△Barry Minto __________ 57.△Mount Kilimanjaro n. __________ https://www.doczj.com/doc/cb10339517.html,panion n. __________ 59.assistance n. __________ 60.congratulate vt. __________ 61.congratulation n. __________ 62.bowling n. __________ 63.graduation n. __________ 64.certificate n. __________ 65.all the best __________ 66.architect n. __________ 67.△Sanders n. __________ 68.adequate adj. __________ 69.access n. __________ 70.accessible adj. __________ 71.△wheelchair n. __________ 72.handy adj. __________ 73.△earphone n. __________ 74.△impair vt. __________ 75.row n. vt . & vi. __________ 76.basement n. __________ 77.outwards adv. __________ 78.exit n. __________ 79.meet with__________ 80.approval n. __________ 81.dignity n. __________ 82.profit n. __________ 83.△italics n.（pl） __________
2019-2020年牛津译林版高中英语必修一Unit 1《School Life》 （Project）教案 【教学目标】 1.to arouse students’enthusiasm for developing after-class activities and forming a school club; 2.to gain the general idea of how to make an attractive poster for the club; 3.to strengthen students ability of putting theory into practice; 4.to guide students to cooperate effectively through group work. 【教学重点】Have students discuss and learn to finish a project by working tog hter 【教学难点】Students should search and find information, and do some writing and drawing by themselves 【教具】Multi-media projector Are you impressed by the soft background music? Step 2 Attract Your Eyes & Grasp Your heart Do you want to experience
(2) Tom in sch ool. e than five courses this term. Jack is no more diligent than John. 杰克和约翰都不勤奋。
湖南文理学院实验报告 时间：2013年12月3日 课程名称：软件项目管理 实验名称：xx学院毕业生就业信息管理系统项目计划书 班级：姓名：同组人： 指导教师评定：签名： 一、实验目的 掌握项目计划书的格式和写作要求，会结合具体项目写作项目计划书。 二、实验要求 1、结合模拟项目写出项目计划书。 2、提交项目计划书一份。 三、实验环境 1．硬件：计算机 2．操作系统：windows平台。 3．相关软件：Microsoft office软件。 四、实验内容 1 引言 1.1 编写目的 为了保证项目团队按时保质地完成项目目标，便于项目团队成员更好地了解项目情况，使项目工作开展的各个过程合理有序，因此以文件化的形式，把对于在项目生命周期内的工作任务范围、各项工作的任务分解、项目团队组织结构、各团队成员的工作责任、团队内外沟通协作方式、开发进度、经费预算、项目内外环境条件、风险对策等内容做出的安排以书面的方式，作为项目团队成员以及项目干系人之间的共识与约定，项目生命周期内的所有项目活动的行动基础，项目团队开展和检查项目工作的依据。 1.2 背景 项目的名称：xx学院毕业生就业信息管理系统。
项目的委托单位：xx学院计算机科学与技术学院软件开发部。 项目的用户（单位）：xx学院各届毕业生。 项目的任务提出者：xx学院计算机科学与技术学院软件开发部。 项目的主要承担部门：xx学院计算机科学与技术学院软件开发部。 项目建设背景：通过本系统可以使xx学院毕业生就业信息管理工作更加合理化、科学化，提高工作的效率，从根本上改变就业管理工作的方式，通过Internet，各院系和学生利用网络的便利，可以直接查询和提交就业信息。在这种系统平台下，可以快速、有效、全面的反映最新的用人单位信息、毕业生基本信息和就业趋势，及时提供高校学生工作管理人员对历届用人单位需求信息的分析统计，及时有效地调查分析大学毕业生的择业趋势和引发的心理问题并进行及时有效的就业指导。可以做到信息的规范管理、科学统计和快速查询，从而减少管理方面的工作量。 1.3定义 Microsoft SQL Server2008：数据库开发环境 Visual Studio 2010：程序开发环境 1.4参考资料 [1]朱少民.软件过程管理.北京：清华大学出版社，2007 [2]朱少民.软件质量保证和管理.北京：清华大学出版社，2007 [3]韩万江，姜立新.软件开发项目管理.北京：机械工业出版社，2004 [4]Harold Kerzner,杨爱华，等.项目管理—计划、进度和控制的系统方法.第9版.北京： 电子工业出版社，2006. 1.5标准、条约和约定 《计算机科学与技术学院毕业生就业信息管理系统立项建议书》 《计算机科学与技术学院毕业生就业信息管理系统项目任务书》 《计算机科学与技术学院毕业生就业信息管理系统项目履行合同》 2、项目概述
高一英语人教新课标必修1重点单词词组归纳总结 必修1 Unit 1 重点单词 1. add vt.增加；添加；补充说vi加；加起来；增添 2. upset vt&vi.使不安；使心烦adj.心烦意乱的；不适的；不舒服的 3. ignore vt.不理睬；忽视 4. calm adj.平静的；镇静的；沉着的vt.&vi.（使）平静；（使）镇静 5. concern vt.关系到；涉及n. 关心；关注；（利害）关系 6. cheat n.欺骗；骗子vt.&vi.欺骗；骗取；欺诈；作弊 7. list vt.列出 8. share vt.分享；均分；分担n.一份；份额 9. series n.连续；系列 10. crazy adj.疯狂的；狂热的 11. purpose n.目的；意图 12. dare vt.&v.aux. 敢；胆敢 13. thunder n.雷；雷声vi打雷；雷鸣 14. entirely adv.完全地；全然地；整个地 15. power n.能力；力量；权力 16. according adv.依照 17. trust vt.&vi.信任；信赖 18. suffer vt.&vi遭受；忍受；经历. 19. questionnaire n.调查表；问卷 20. quiz n.测验；提问vt. 对…进行测验 21. situation n.情形；境遇；（建筑物等的）位置
22. communicate vt.交际；沟通；传达（感情、信息等） 23. habit n.习惯；习性 重点短语 1. Calm down 平静下来；镇定下来 2. Be concerned about 关心；挂念 3. Make a list of 列出… 4. Be crazy about 对…着迷 5. According to 根据…所说；按照 6. Get along with 与…相处；进展 7. Fall in love 相爱；爱上 8. Try out 试验；试用 9. add up 合计 10. set down 放下；记下；登记 11. get sth. done 做…；使…被做； 12. share sth. with sb. 和某人分享某物 13. go through 经历；经受； 14. a series of 一连串的；一系列；一套 15. on purpose 故意 16. in order to 为了… 17. join in 参加；加入 18. communicate with 和…交流 19. face to face 面对面地 20. suffer from 遭受。。。 必修1 Unit 2 重点单词
北大青鸟网上商城系统项目开发计划
J2EE第三小组 目录 1．引言 (2) 1.1编写目的 (2) 1.2项目背景 (3) 1.3定义 (3) 1.4参考资料 (3) 2．项目概述 (5) 2.1工作内容 (5) 2.2条件与限制 (5) 2.3产品 (5) 2.4运行环境 (5) 2.5服务 (6) 2.6验收标准 (6) 3．实施计划 (7) 3.1任务分解 (7) 3.2进度 (7) 3.3预算 ...................................................................................... 错误！未定义书签。 3.4关键问题 ............................................................................... 错误！未定义书签。4．人员组织及分工. (7) 5．交付期限 (8) 6．专题计划要点 (8) 1．引言 1.1编写目的 本计划提供一份合理的项目开发进程表,使所有的开发人员任务明确,步调一致,最终共同准时的完成项目.软件工程的目标是提高软件质量,本计划也是从软件的正确性,性能,易用性,灵活性,可重复性,可理解性等各个方面出发,以提高软件质量为最终目的而制定.读者为参与开发的所有相关人员.
1.2项目背景 说明： A、软件系统的名称：北大青鸟网上商城系统 B、任务提出者：北大青鸟J2EE九月班第三小组 C、开发者：北大青鸟J2EE九月班第三小组 实现完成的系统将作为北大青鸟珠在线销售系统使用，所应用的网络为Internet网络。 D、本系统将是独立的系统，所产生的输出独立。 本系统将使用Oracle9i作为数据库存储系统. 1.3定义 1.4参考资料 相关的文件包括： A、内部文件《北大青鸟网上商城电子商务系统案例研究项目》； B、北大青鸟网上商城电子商务系统案例研究项目分析会议备忘录； C、《北大青鸟网上商城电子商务系统案例研究项目可行性分析》； 参考资料： A、北大青鸟Aptech ACCP3.0 Y2《基于软件开发项目的毕业设计》； B、国家标准《软件需求说明书（GB856T——88）》； C、亚马逊网站的软件需求说明； 合同： A、《北大青鸟网上商城电子商务系统案例研究项目合同20040510 - 2》；