Ancient and Medieval Political Theory Assignment

Ancient and Medieval Political Theory - Assignment Example Aquinas in the theory hypothesized the concept of nature to help society members understand that there is a supernatural being beyond this earth. Aquinas further argues that the world is merely a resting bay after which humans move to another life. This concept outstands in the Thebes society when various characters keep invoking the punishment sinners will receive from gods after death. Creon’s wife, Eurydice commits suicide cursing the husband and expressing her wish for god’s punishment upon the death of the husband. The blind prophet Tiresias brings the supernatural concept by claiming prophesies of god’s desires and anger to the king. The concepts solve the conflict between the church and the human freedom to think. It shows that the actions of the worldly authority must reconcile with the wishes of the church for harmonious coexistence. The concept of sovereignty is the source of law. Based on political ideologies and tenets, sovereignty rests with the people’s power. Based on theological points of view, however, sovereignty originates from God. It, therefore, gives individuals the freedom to make decisions without autocracy from rulers and the church. The concept of supremacy of the church also creates harmony between the church and the government. Creon, the dictator who does not obey the will of his people, chorus later comes to lament when his son Haemon and wife commits suicide for his actions. Disobedience of sovereignty attracts heavy punishment from God irrespective of who you are in the

IT Project Management Approaches Coursework Example | Topics and Well Written Essays - 1500 words

IT Project Management Approaches - Coursework Example It narrows down from the above two and looks at some of the specific applications in the information Technology field by looking at the Software development life cycle approach that is part of the traditional approach. It goes further in the agile approach to look at specific applications of the approach to the field of information technology. The paper also compares the two approaches by looking at their strengths and weaknesses and the type of projects to which they can be used/ applied and why they will or will not work. 1. The traditional/phased approach to project management The traditional approach to project management involves very well-organized and deliberate planning and control methods. In this approach there are distinct project life cycle stages or phases which are easily recognizable as one leads directly to another. Tasks are completed in in an orderly sequence, one after the other and this necessitates that a significant part of the entire project is planned before t he process begins (Hass, 2007,pp1-8). This model assumes that all events affecting the entire project are predictable and that the tools and the tasks undertaken by each individual are well understood. With this approach it assumes that once a phase is complete it will not be revisited, which is not the case for many projects especially IT projects. This model is forms the basis for the phased methodology used in many projects. The approach has taken many dimensions especially in the field of information technology with various sub models coming up from this traditional/phased model (Hass, 2007,pp1-8). The advantage of this approach is that it sets out the phases for development and stresses the importance of requirements for each stage. On the other hand the limitation is that projects rarely follow the sequential flow and many stakeholders find it difficult to define all the requirements for a project at the beginning(Hass, 2007,pp1-8). The approach has the following distinct stag es: initiation, planning and design, execution and construction, monitoring and controlling systems and finally the completion stage. It is important to note that not all projects will go through all the stages mentioned above some may be terminated before they get to the completion stage. 1.1. The Software Development Life Cycle (SDLC) In information technology projects, this phased approach can be compared to the software development life cycle approach (SDLC). This approach is composed of the following distinct stages that must be followed to come up with working software: planning, requirements definition, design, development, integration and testing and finally installation and acceptance (Radack, 2009, pp1-7). The planning stage aims at establishing a bird’s eye view of the proposed software product and uses this to form the basic project organization, assess feasibility and risks associated with the project and define suitable management and technical approaches. The m ost critical part concerning this stage is the listing of goals of the project and this is done before anything else (Radack, 2009, pp1-7). The requirement definition stage begins immediately the goals in the planning stage are identified. Each of these goals is then refined into a set of requirements which define the major functions of the proposed application and also define the initial data entities.