follow me on Twitter

    Subscribe to
    Posts [Atom]


    Alternative Words

    Thursday, February 28, 2008

    SpeechparlancenomenclatureSelflessnessAltruisticWordyVerbosePedanticThinkMullTeachIndoctrinateInculcateBooktomeKnowledgeEruditeSkillAcumenConfirmAscertainUntiringUndefatigableYearAnnumUnprincipledreprobateUnderstandableintelligibleCommunicationdiscourseAnalyzeexplicateVerbal AttackPolemicImproveEdifyGreedAvariceGet used toInureAccustomHelpUnder the Auspices ofinclinationpenchantdoubtfulapocryphalcredibleplausiblecontradictionantinomyproportionalpro ratauntil nowhithertoprinciplepostulateappearancesemblancesmall detailminutiafoolish talkprattleannoyvexnot correctableincorrigibletrick / trickeryartificechicaneryhappinesslfelicityfoodvictualvittlehonest or moralprobityprincipledscrupulousarrogantinsolentfollyyicerefrainforbearproperlyarightclaimpurportlong speech scoldharanguefreegratisdefamatoryscurriloussubtle harmperniciousnegligentremissmoney sentremittanceinstillinculcateprepared speechextemporaneousstylevoguemake uneasydiscomfitclimbclamberread thoroughlyperusehostileinimicaldrinking alcoholtipplefireconflagrationmercyclemencyharsh weatherinclemencieslazyindolentgoodbenevolentprofitemolumentjokingjocoseplancontrivedeviseinventplotinadequatescantmeagerproductivefruitfulprolificpeacefulamicableopposed incompatibleantitheticaldrive reactantimpetusstimulusrepayremuneraterecompenseambiguousequivocalslandercalumniateheld permanentlyvestedlessenreduceabatemitigategetobtainprocuresurrenderyieldcedecapitulatewillingnessalacrityuprisingriottumultoutbreakcommotiondestroyremoveextirpateexterminateattributeaccreditassignascribeapprovalapprobationassumptionhypothesissuppositionreprimandcensurecriticizereproachwickedreprobatedissaproveoriginalprototypearchetypesharpacuteintensecrucialextremesuperficially pleasing specioussophisterstrugglestrifecontentionsharpcausticcriticaltartagreeassentacquiesceconcurspeedswiftnesscelerityreproachfaultblamequarrelsomepugnaciousbelligerentcombativeimmoralsordidignoblebasevileurgeadvisewarnexhortslandermalign defameperniciousbalefulinjurious quarrelsomedissentiouscontentiousquarrelsomefactioussympathysorrowempathizepitycommiseratewealthyprosperousaffluentimpliedtacitfruitfulprolificspreadpervasiveambushambuscadeskillprowessvalorbravery abilitystrength predictforetellforebodepredictportendpredicthintimplysuggestcleveradroitdexteroussevereinclementsevereroughharshstormymercilesseasilyswimminglyeffortlesslyfew wordsterselaconicplayful banterflirtybadinageconfidenceassuranceaplombfastenergeticfreneticstupid personidiotdoltsettle cozyensconcesettle snugglyblameworthyreprehensibleclearvividlucidhaterepugnanceaversiondetestloatheabominateabhorfearlessdauntlessintrepidculminationzenithhighest pointremainexistsubsistwrongimproperamissfaulty hinder impedeencumberhamperretardburden short lived ephemeral professorshiptutelageinstruction lawlesswantonunrestrainedloose raidpillagemaraudinvasionforaylasciviouslewd seperatedisparatecompositecompound beatbeatwhipreprimandberatecensureexcoriate apatheticlanguidspiritlessindifferentlistless strivecontendvie sorrowfuldolorouslachrymose grow togetheraccreteadhere overtake by darknessbenightfloodoutpouringinundationspateslendersveltelithe.suaveurbaneversatilechangeableprotean pacified appeased forgivingplacable untiring undefatigable stubborn manageableobstinateintractable avoid eschewabstainshunavoid surround besetbeleaguer unchangeable immutable sharp incisivetrenchantkeensharpsmart sharp incisiveintellect secret covertclandestine quiet restquiescencestillinactivemotionless widespread pervadespread out proclaim publishproclaimdecreepromulgate remainder marktracevisible evidencevestige unrestricted freeunfettered embellished elaboratedwrought enthusiasm vitalityexuberance inclination propensitytendency prevail crossget oversurmount sustain encouragebuoy disbelief incredulousskepticalunbelief reviseeditredaction guessthinksurmiseopinionconjecture beginningdevelopingburgeoningnascent self-generatingself-sustainingbootstrap descendantheirscion melancholywistfullongingyearningpensive lastingperennialcontinuingrecurrenteverlastingperpetual assistantfolloweracolyte passionzealardorfervor freeuncheckedunfetteredunrestricted systembuildingorganizationedifice cancel
    rescind
    nullify
    abrogate
    revoke
    void
    invalidate
    purposeless
    idle
    vacuous

    Labels:


    How to do a screen shot in Mac OS X

    Saturday, February 23, 2008

    entire screen - Command-Shift-3.
    region of the screen - Command-Shift-4

    And you can always use the macs Grab tool (which in my opinion sucks because of its inability to work with other applications simultaneously)

    Labels:


    The AutoScheduler

    Friday, February 15, 2008

    Vision


    Problem: students at institutions have to search through a quagmire of course and class schedule information. When the student does find a desired course ,many times they have no idea if the course they need to take will even advance them towards graduation. Lastly, a student has to find the balance between this "right" course and their own personal schedule. All these sources of information reside in different places and referencing them is not seamless.

    Vision Statement: an inuitive scheduling tool for the purpose of taking the effort out of scheduling, that will tame course and class schedule data in a manner that is reflective of a student's personal schedule and progress toward degree needs in seamless, intuitive, and integrated tool.

    Main Parties Involved:
    Individual Developers
    Project Managers

    Use Cases:
    from the student plan builder gather necessary courses for a term
    setup calendar for student schedule planning
    create view for course/class schedule
    establish means of registration


    Plan


    Inception February 19
    Vision
    Plans
    Business Case
    Risks
    -- Lifecycle objective Milestone (agreement from dave)

    Elaboration February 20
    define architecture
    get more information for a better plan
    Present Prototype (confirm only since its been approved)
    -- Life cycle Architecture milestone (if we choose whether to go ahead with the project as planned)

    Construction February 21
    Design
    Code
    Test
    --Initial Operational Capability (user tries software)

    Transition March 15

    Risks


    Peoplesoft registration role may be on paternity leave
    Client may want registration in a non optimal manner (unseamlessly move to peoplesoft registration).

    Labels:


    The RUP


    Principles of The RUP

    Attack major risks early
    Deliver value
    Focus on executable software
    Allow change
    Establish an architecture
    Componentize
    Work as a team
    Quality

    Rup is irerative as opposed to waterfall.

    static structure of rup:
    activites, roles, disciplines, artifacts

    dynamic structure of rup
    time/phases: inception, elaboration, construction, transition

    Subsequent Milestones
    Lifecycle objective milestone
    Lifecycle architecture milestone
    Initial operation capability milestone
    Product milestone

    Objectives of the Inception Phase
    Understand what to build
    Identify key system functionality
    Determine at least one possible solution
    Understand the cost schedule and risks
    Decide what process to follow and what tools to use.

    Lifecycle Object Milestone Criteria
    Stakeholder agreement on scope and initial cost schedule estimate
    Agreement that the right requirements hve been captured
    Agreement that the cost/schedule estimate, priorities, risks, and developement process are appropriate
    Have identified risks and a mitigation strategy has been defined

    Objectives of the Elaboration Phase
    get a more detailed understanding of the requirements
    design, implement, validate, and baseline the architecture
    Mitigate essential risks, and produce more accurate schedule and cost estimates
    refine the developement case and put the developement environment in place


    Lifecycle Architecture Milestone Criteria
    vision and requirements are stable
    architecture is stable
    approaches to testing and evaluation are proven
    executable prototype shows the major risks have been addressed and resolved
    construction plans are sufficient
    iteration plans for construction phase have credible estimates
    stakeholders agree the vision can be met by current architecture
    actual resources are acceptable in terms of planned resources

    Objectives of the Construction Phase
    Minimize developement costs and achieve some degree of parallelism
    Scale up the project
    Build and assess several internal releases
    Iteratively develop a complete product that is ready to transition to its user community

    Initial Operation Capability Milestone Criteria
    product release is stable and mature enough to be released in the user community
    stakeholders are ready for transition into the user community
    actual resources are still acceptable in terms of planned resources

    Objectives of the Transition Phase
    Beta test to validate user expectations are met.
    Train users and maintainers to achieve user self-reliability
    Prepare deployment site and convert databases
    prepare for launch packaging, production and market rollout; release to sales force; personnel training
    Achieve stakeholder agreement that deployment baselines are complete and consistent with vision
    Improve project performance through lessons learned

    Product Release Milestone Criteria
    The user is satisfied
    actual resources are acceptable in terms of planned resources and if not what can aid this in the future

    Key modeling elements of the RUP
    roles - how the individual should do the work
    activity - a unit of work that one in role is to perform usually effecting an artifact
    artifact - a piece of info that is produced modified or used by a process
    workflow - adds meaning to sequence of activities that produce value and show interaction between roles.
    disciplines - are high level workflows and containers for roles, activities and artifacts
    workflow details - workflows within a discipline
    usecase- a section in the future user manual for the system under developement
    low ceremony - low documentation and formalism in the procedure
    high ceremony - comprehensive documentation and traceability maintained between artifacts, change control boards, etc.
    Agile - low ceremony
    disciplined - high ceremony
    discipline - partition of activities by type
    baseline - A specification or product that has been formally reviewed and agreed upon, that serves as the basis for further development, and that can be changed only through formal change control procedures.
    Development Cycle - one pass through the four RUP phases
    Development Case - a brief description of how your project should use your RUP Configuration
    RUP Process Component - a module of process knowledge
    RUP Library - a collection of process components out of which a set of RUP Process Configuration may be compiled
    RUP Base - a collection of process components meant to be extended by applying plugins to generate RUP process configurations. It resides in a RUP library
    RUP Plugin - a unit for one or several process components that can extend a RUP base


    The RUP Phases
    Inception
    Objectives of the inception phase
    Understand what to build - determine vision, scope, and boundaries
    Identify key system functionality - determine which ways of using the system are critical
    determine at least one possible solution - decide on a candidate structure
    Undertand Costs, Schedules, and risks
    Decide on what process to follow and what tools to use.

    Introducing The RUP to a project
    Assess
    Plan
    Configure and customize
    Execute
    Evaluate

    How to delete an operating system from dual boot in windows

    Thursday, February 14, 2008

    How to remove one Windows XP when two or more Windows XPs are installed on the same partition.

    It's vital to accurately identify two items that relate to the XP you wish to REMOVE:
    a The name of its installation folder/directory (we will remove that folder).
    b Which is its line in the boot file Boot.ini (we will remove that line).
    Optionally first create, and test, a Rescue Boot Disk for your current situation (1 floppy disk).
    Skip the next section if you cannot boot to the Windows XP to be REMOVED
    (though you should try editing Boot.ini to make it bootable!).
    Boot to the Windows XP you wish to REMOVE.
    and note its position in the Boot Menu during bootup.
    Uninstall any software/applications that are specific to only this Windows XP.
    Now go to Start > RUN. Type in (and then press OK).
    CMD
    Type in, and then press [Enter]
    echo %windir%
    You will see the name of the Windows folder you are using and you wish to REMOVE.
    Note that name and then exit the Command Prompt.
    Boot to a Windows XP you wish to KEEP
    and note its position in the Boot Menu during bootup.
    Make sure this Windows is the Default option in the Boot Menu
    (the Windows to be removed MUST NOT be the Default in the Boot Menu).
    Now go to Start > RUN. Type in (and then press OK).
    CMD
    Type in, and then press [Enter]
    echo %windir%
    You will see the name of the Windows folder you are using and you wish to KEEP.
    Note that name and then exit the Command Prompt.
    Backup Boot.ini (it's a Hidden file, usually on drive C:).
    Now edit Boot.ini (see also on this page) and remove the line referring to the XP installation you wish to REMOVE
    - the order in Boot.ini is the same as you see in the Boot Menu and you also now know the name of the Windows XP folder(s) you wish to keep.
    Reboot.
    Make sure you boot directly to a Windows XP you wish to KEEP.
    If that XP does not boot, restore your backup of Boot.ini, and start at step 3 again.
    Use Windows Explorer to identify the Windows folder you wish to REMOVE
    and then RENAME the Windows folder you wish to REMOVE
    (right-click on the correct folder/directory and click Rename, and then rename it).
    Test all the software and applications you wished to keep.
    If you are not happy with the situation, return the original name to the renamed folder and also restore the original Boot.ini, and then start at step 3 again.
    If all is satisfactory, DELETE the RENAMED Windows folder - that's the Windows XP to be REMOVED.
    Caution: DO NOT delete ANY boot files.
    Caution: DO NOT interfere with the 'Documents and Settings', or 'Program Files', or any other folders except the Windows XP folder to be removed.

    Advise: You can now recreate the Rescue Boot Disk to reflect your new situation.

    Labels: